Triple
T25240334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T’Pol |
E632445
|
entity |
| Predicate | nationalityEquivalent |
P163826
|
FINISHED |
| Object | Vulcan (planetary) |
—
|
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: Vulcan (planetary) | Statement: [T’Pol, nationalityEquivalent, Vulcan (planetary)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalityEquivalent Context triple: [T’Pol, nationalityEquivalent, Vulcan (planetary)]
-
A.
countryEquivalent
Indicates that two country entities are considered equivalent or represent the same country in the given context.
-
B.
nationalityInText
Indicates that a person's nationality is mentioned or specified within a given text.
-
C.
nationalityInWorld
Indicates that an entity has a specific national affiliation or citizenship within the world context.
-
D.
equivalentEthnonym
Indicates that two different ethnonyms refer to the same ethnic group or people.
-
E.
nationalityAdjectiveOf
Indicates that one term is the adjectival form derived from the nationality associated with the other term.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 21, 2026, 1:07 p.m.