Triple
T21731088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Figure Eight Pools |
E536405
|
entity |
| Predicate | hasApproximateWalkDistance |
P37106
|
FINISHED |
| Object | about 6 km return from Garawarra Farm |
—
|
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: about 6 km return from Garawarra Farm | Statement: [Figure Eight Pools, hasApproximateWalkDistance, about 6 km return from Garawarra Farm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateWalkDistance Context triple: [Figure Eight Pools, hasApproximateWalkDistance, about 6 km return from Garawarra Farm]
-
A.
hasApproximateWalkingTimeTo
Indicates that there is an estimated or approximate amount of time it takes to walk from one entity to another.
-
B.
approximateDistanceFrom
chosen
Indicates an estimated or rough measure of how far one entity is from another.
-
C.
hasApproximateDistanceScale
Indicates that one entity is related to another by a distance measure that is approximate or estimated rather than exact.
-
D.
hasWalkingPathLength
Indicates the length or distance of a designated walking path associated with an entity.
-
E.
hasWalkingPathAround
Indicates that one entity has a walking path that encircles or runs around another 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69effd0713c48190a38b3963cb3cbaf0 |
completed | April 28, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:48 p.m.