Triple
T13471013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ormiston Gorge |
E311628
|
entity |
| Predicate | hasDayUseArea |
P110503
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ormiston Gorge, hasDayUseArea, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDayUseArea Context triple: [Ormiston Gorge, hasDayUseArea, yes]
-
A.
hasCentralAreaUse
Indicates that an entity’s central area is used or designated for a particular function or purpose.
-
B.
hasAreaType
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
-
C.
hasParkArea
Indicates that an entity includes or is associated with a designated park or recreational area within its boundaries.
-
D.
hasIndoorArea
Indicates that an entity possesses or includes an area or space that is located indoors or within a building.
-
E.
hasFloorArea
Indicates that an entity possesses a specified amount of floor space as a measurable area.
- F. None of above. chosen
Provenance (4 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf22e5f88190b1078f006c8ef7c0 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:42 p.m.