Triple
T6066772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LR-87 |
E135178
|
entity |
| Predicate | laterOxidizer |
P68455
|
FINISHED |
| Object | nitrogen tetroxide |
—
|
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: nitrogen tetroxide | Statement: [LR-87, laterOxidizer, nitrogen tetroxide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterOxidizer Context triple: [LR-87, laterOxidizer, nitrogen tetroxide]
-
A.
laterBase
Indicates that one event, state, or version occurs or is valid at a later time than another referenced event, state, or version.
-
B.
laterPromoter
Indicates that one promoter occurs or becomes active at a later time than another promoter in a regulatory or temporal sequence.
-
C.
laterComplementedBy
Indicates that an earlier entity is subsequently supplemented, enhanced, or completed by a later entity.
-
D.
laterNamed
Indicates that an entity was given a new name at a later time, linking its original identity to its subsequent name.
-
E.
laterIn
Indicates that one event, state, or time point occurs after another in temporal order.
- 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_69c00879e8048190b690717d19c5bc03 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0573f17088190a728f1c290cc9d1d |
completed | March 22, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69c049f031408190b08b2766237c5dd0 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8d4a148190bd8f95caae978e1b |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:10 p.m.