Triple
T21774702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | POT |
E537539
|
entity |
| Predicate | successorAbbreviation |
P35289
|
FINISHED |
| Object | PST |
—
|
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: PST | Statement: [POT, successorAbbreviation, PST]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAbbreviation Context triple: [POT, successorAbbreviation, PST]
-
A.
abbreviationOfSuccessor
chosen
Indicates that one entity is an abbreviation or shortened form of another entity that is the successor in some sequence or versioning.
-
B.
shortNameOfSuccessor
Indicates that one entity is the abbreviated or short name used to refer to its successor entity.
-
C.
successorLabel
Indicates that one entity is the direct successor or next in sequence to another entity, often inheriting its role, position, or label.
-
D.
successorAdministrativeName
Indicates that one administrative entity’s name has been replaced by another name that now serves as its official administrative designation.
-
E.
successorPrefix
Indicates that one sequence is formed by taking another sequence and replacing its final element with its immediate successor, while keeping all preceding elements identical.
- 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f04627bd488190bbc1fde8db417b55 |
completed | April 28, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:51 p.m.