Triple
T32095758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taniquetil |
E819717
|
entity |
| Predicate | topHas |
P173549
|
FINISHED |
| Object | Ilmarin |
—
|
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: Ilmarin | Statement: [Taniquetil, topHas, Ilmarin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topHas Context triple: [Taniquetil, topHas, Ilmarin]
-
A.
top
Indicates that one entity is physically positioned above or on the uppermost surface of another entity.
-
B.
topForward
Indicates that one entity is positioned or oriented in front of and above another entity along a forward-facing direction.
-
C.
hasTopness
Indicates that an entity possesses the quantum property of topness, typically associated with the presence or contribution of a top quark.
-
D.
topLocation
Indicates that one location is the primary, highest-level, or most prominent place associated with another entity or set of locations.
-
E.
topper
Indicates that one entity is the highest-ranking or best-performing among a set, often in a competitive or comparative context.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b64194148190ad2f84e111f66de0 |
completed | May 3, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:26 a.m.