Triple
T4575770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APB Opinions |
E123137
|
entity |
| Predicate | statusUnderASC |
P58066
|
FINISHED |
| Object | superseded and incorporated into Codification |
—
|
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: superseded and incorporated into Codification | Statement: [APB Opinions, statusUnderASC, superseded and incorporated into Codification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusUnderASC Context triple: [APB Opinions, statusUnderASC, superseded and incorporated into Codification]
-
A.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
B.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
C.
statusInLogic
Indicates the logical status or role an entity holds within a formal reasoning or inference context.
-
D.
statusLevelAbove
Indicates that one entity’s status level is higher or more advanced than another entity’s status level.
-
E.
rankStatus
Indicates the hierarchical level or position an entity holds within an ordered ranking or status system.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58dfe3508190b21836079e951a3c |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b4a9508190acdb888eef18f1ee |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:10 p.m.