Triple
T29645551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Emerald Pool |
E755988
|
entity |
| Predicate | hasHigherPart |
P83691
|
FINISHED |
| Object | Middle Emerald Pool |
—
|
NE NERFINISHED |
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: Middle Emerald Pool | Statement: [Lower Emerald Pool, hasHigherPart, Middle Emerald Pool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHigherPart Context triple: [Lower Emerald Pool, hasHigherPart, Middle Emerald Pool]
-
A.
hasHigherClass
Indicates that one entity belongs to a higher rank, level, or category in a hierarchy than another entity.
-
B.
hasUpperPartFrom
chosen
Indicates that an entity includes, incorporates, or is composed of an upper part originating from another entity.
-
C.
hasHigherInstance
Indicates that one instance in a hierarchy or ordering is ranked or valued higher than another instance.
-
D.
isHigherThan
Indicates that one entity has a greater value, level, or position than another entity.
-
E.
hasHigherFamily
Indicates that one entity belongs to a family or familial group that is ranked or positioned above another entity’s family in a hierarchy or comparative structure.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: April 28, 2026, 6:49 p.m.