Triple
T3608093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greek fire |
E76419
|
entity |
| Predicate | possibleComponent |
P9772
|
FINISHED |
| Object | petroleum |
—
|
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: petroleum | Statement: [Greek fire, possibleComponent, petroleum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleComponent Context triple: [Greek fire, possibleComponent, petroleum]
-
A.
componentType
Indicates that one entity specifies or classifies the kind or category of component that another entity represents or uses.
-
B.
component1
Indicates that one entity functions as a constituent or part of another entity within a larger whole.
-
C.
usedComponent
chosen
Indicates that one entity has employed or incorporated another entity as a component in its structure, function, or operation.
-
D.
isCoreComponentOf
Indicates that something is an essential, foundational part required for the structure, function, or identity of another entity.
-
E.
plannedComponent
Indicates that one entity is intended or scheduled to serve as a component or part of another entity in a planned or future configuration.
- 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc228e24481909ae6a1e4ad796917 |
completed | March 8, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69adb83d8b1c8190b3bddbc5dc995a87 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.