Triple
T23056333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five Phases theory |
E574164
|
entity |
| Predicate | hasGeneratingRelation |
P51370
|
FINISHED |
| Object | wood generates fire |
—
|
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: wood generates fire | Statement: [Five Phases theory, hasGeneratingRelation, wood generates fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeneratingRelation Context triple: [Five Phases theory, hasGeneratingRelation, wood generates fire]
-
A.
hasGenerationRelationship
chosen
Indicates that one entity is involved in producing, creating, or giving rise to another entity.
-
B.
hasGeneratingFunction
Indicates that one entity serves as the generating function associated with, or defining, another entity.
-
C.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
D.
hasGeneratorType
Indicates that an entity is associated with or uses a specific type or category of generator.
-
E.
belongsToGeneration
Indicates that an entity is associated with, classified within, or a member of a particular generation or generational group.
- 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_69e245ba7ae48190be606dbc54120e39 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1868099708190b23725dc8a305e09 |
completed | April 29, 2026, 4:18 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:55 p.m.