Triple
T4193282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sethlans |
E89083
|
entity |
| Predicate | elementAssociated |
P53226
|
FINISHED |
| Object | 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: fire | Statement: [Sethlans, elementAssociated, fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elementAssociated Context triple: [Sethlans, elementAssociated, fire]
-
A.
associatedWithElement
Indicates a relationship where one entity is linked or connected to a particular element, such that the element is relevant to, involved in, or characteristic of that entity.
-
B.
elementalAssociation
chosen
Indicates an association where one entity is linked or related to a particular element or elemental property (such as fire, water, earth, or air).
-
C.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
D.
leaderAssociatedWith
Indicates a relationship where a leader is connected or affiliated with a particular entity, such as an organization, group, or cause.
-
E.
attachedTo
Indicates that one entity is physically or logically fastened, connected, or joined to 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_69aed9569a4481908b6c1fcec2a11e21 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af04b009dc8190abda3f149a5b16fa |
completed | March 9, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69af01935064819096b7619f42e164dd |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:46 p.m.