Triple
T9702821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argo |
E234819
|
entity |
| Predicate | constructedWithMaterial |
P21333
|
FINISHED |
| Object | talking oak from Dodona |
—
|
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: talking oak from Dodona | Statement: [Argo, constructedWithMaterial, talking oak from Dodona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructedWithMaterial Context triple: [Argo, constructedWithMaterial, talking oak from Dodona]
-
A.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
B.
createdByConstructionOf
Indicates that something comes into existence as a result of a construction process or building activity performed by an agent.
-
C.
hasReconstructionMaterial
Indicates that something is associated with, composed of, or utilizes a particular material for its reconstruction.
-
D.
constructionUsed
Indicates that one entity was employed as a construction method, material, or component in creating or assembling another entity.
-
E.
madeWith
chosen
Indicates that one entity is created, produced, or constructed using another entity as a material, ingredient, or component.
- 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_69ca84cc78808190a56f3402b7c139a7 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d7283188190bd50e18f643ad0d3 |
completed | April 1, 2026, 10:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03b641408190942464eaf174c6b5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:18 p.m.