Triple
T15740086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leontice |
E381577
|
entity |
| Predicate | hasUndergroundOrgan |
P120429
|
FINISHED |
| Object | tuber |
—
|
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: tuber | Statement: [Leontice, hasUndergroundOrgan, tuber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUndergroundOrgan Context triple: [Leontice, hasUndergroundOrgan, tuber]
-
A.
hasUndergroundMine
Indicates that one entity possesses, controls, or contains an underground mine associated with it.
-
B.
hasUndergroundLevel
Indicates that one entity possesses or includes a level, floor, or section that is located below ground level.
-
C.
hasUndergroundDepth
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
-
D.
integratedIntoUnderground
Indicates that something has been incorporated or absorbed into an underground system, structure, or environment.
-
E.
hasUnderpass
Indicates that one location or structure includes or is connected by an underpass beneath another feature or pathway.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0052c6208819098165d61d378d13b |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e0b4d01c9c81909f6b611e8144c838 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 10, 2026, 4:46 a.m.