Triple
T4671827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | clear and present danger test |
E103580
|
entity |
| Predicate | replacedOrNarrowedBy |
P101
|
FINISHED |
| Object | imminent lawless action test |
—
|
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: imminent lawless action test | Statement: [clear and present danger test, replacedOrNarrowedBy, imminent lawless action test]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedOrNarrowedBy Context triple: [clear and present danger test, replacedOrNarrowedBy, imminent lawless action test]
-
A.
wasSupersededBy
chosen
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
B.
supersededInPrecisionBy
Indicates that one entity’s level of precision has been replaced or overtaken by another entity’s greater precision.
-
C.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
D.
partlyReplacedBy
Indicates that one entity has been superseded or substituted in part, but not entirely, by another entity.
-
E.
mayBeReplacedBy
Indicates that one entity can potentially be substituted or superseded 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_69bd43dda32c8190938b37744ca270fc |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6215864c8190b50ba0f63ba87d0c |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.