Triple
T28529712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IPRA |
E722005
|
entity |
| Predicate | establishedAsReplacementFor |
P114659
|
FINISHED |
| Object | Office of Professional Standards |
—
|
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: Office of Professional Standards | Statement: [IPRA, establishedAsReplacementFor, Office of Professional Standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsReplacementFor Context triple: [IPRA, establishedAsReplacementFor, Office of Professional Standards]
-
A.
developedAsReplacementFor
chosen
Indicates that one entity was created or designed specifically to take the place of another entity, serving as its successor or substitute.
-
B.
replacedOnPlatformBy
Indicates that one entity has been superseded or taken over by another entity on a particular platform.
-
C.
oftenReplacedBy
Indicates that one entity is frequently substituted or superseded by another in similar contexts or uses.
-
D.
replacedSystemUsedUntil
Indicates that one system was used up until it was replaced by another system.
-
E.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 28, 2026, 3:27 a.m.