Triple
T711958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taphus |
E14227
|
entity |
| Predicate | hasCurrentStatus |
P13923
|
FINISHED |
| Object | defunct name |
—
|
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: defunct name | Statement: [Taphus, hasCurrentStatus, defunct name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrentStatus Context triple: [Taphus, hasCurrentStatus, defunct name]
-
A.
hasActivityStatus
chosen
Indicates the current state or condition of an activity, such as whether it is planned, ongoing, completed, or cancelled.
-
B.
hasCurrent
Indicates that an entity presently possesses, exhibits, or is associated with a particular state, attribute, or resource at the current time.
-
C.
hasStatusIn
Indicates that an entity holds or is assigned a particular status within a specified context, scope, or system.
-
D.
hasStatusLabel
Indicates that an entity is associated with a specific status expressed as a human-readable label.
-
E.
exportStatus
Indicates the current state or outcome of an entity’s export process (e.g., pending, in progress, completed, or failed).
- 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_69a4934a36e081909e7abef98b898a4e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a77fcc6881908a025bb21e44ad56 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f221b081909fbaa689fb20eb3e |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:36 p.m.