Triple
T32256591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orion 38 |
E824041
|
entity |
| Predicate | burnMode |
P173888
|
FINISHED |
| Object | single-burn |
—
|
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: single-burn | Statement: [Orion 38, burnMode, single-burn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burnMode Context triple: [Orion 38, burnMode, single-burn]
-
A.
burnCapability
Indicates that an entity has the ability or potential to burn, ignite, or cause combustion under certain conditions.
-
B.
burnProfile
Indicates that one entity records or defines how another entity burns, such as its combustion characteristics or burn behavior.
-
C.
burnTiming
Indicates the temporal characteristics or schedule associated with a burning event or burn-related process.
-
D.
isBurning
Indicates that an entity is currently on fire or undergoing combustion.
-
E.
burnsWhen
Indicates that one entity causes another entity to ignite or combust when they come into contact or under specified conditions.
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bc549ce88190963037034412e0b1 |
completed | May 3, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:41 a.m.