Triple
T35145497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayish Bayou |
E1014817
|
entity |
| Predicate | hasGeographicFeatureCode |
P12436
|
FINISHED |
| Object | stream |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: stream | Statement: [Ayish Bayou, hasGeographicFeatureCode, stream]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeographicFeatureCode Context triple: [Ayish Bayou, hasGeographicFeatureCode, stream]
-
A.
hasGeographicType
Indicates that an entity is associated with or classified by a specific type or category of geographic feature or area.
-
B.
hasGeographyCharacteristic
chosen
Indicates that an entity possesses a specific geographical feature, property, or attribute.
-
C.
isGeographicCode
Indicates that one entity functions as a geographic code that identifies or represents the location of another entity.
-
D.
hasGeographicalCoordinateSystem
Indicates that something uses or is defined within a specific geographical coordinate system for locating positions on the Earth’s surface.
-
E.
hasGeocode
Indicates that an entity is associated with a specific geographic coordinate or coded location reference.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: May 3, 2026, 4:02 p.m.