Triple
T36946395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qaraoun |
E913922
|
entity |
| Predicate | hasNearbyBirdHabitat |
P198150
|
FINISHED |
| Object | Lake Qaraoun bird area |
—
|
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: Lake Qaraoun bird area | Statement: [Qaraoun, hasNearbyBirdHabitat, Lake Qaraoun bird area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyBirdHabitat Context triple: [Qaraoun, hasNearbyBirdHabitat, Lake Qaraoun bird area]
-
A.
hasNearbyHabitats
Indicates that one entity has other habitats located close to it in geographic or spatial terms.
-
B.
hasNearbyBirdStation
Indicates that one entity is located close to a bird observation or monitoring station associated with another entity.
-
C.
hasNearbyWildlife
Indicates that there is wildlife located close to or in the immediate vicinity of the referenced entity.
-
D.
hasNearbyEcosystemType
Indicates that one entity has an ecosystem of a specified type located in its immediate surrounding area.
-
E.
nearbyBirdlife
chosen
Indicates that there are birds present in close proximity to the referenced location or entity.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0079e152648190a9da2add94fc1831 |
completed | May 10, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_6a0078f77f9c8190af357a6016a2bd53 |
completed | May 10, 2026, 12:24 p.m. |
Created at: May 3, 2026, 4:13 p.m.