Triple
T38288360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young Tod |
E1022283
|
entity |
| Predicate | relationshipArcWithCopper |
P204580
|
FINISHED |
| Object | tragic friendship |
—
|
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: tragic friendship | Statement: [Young Tod, relationshipArcWithCopper, tragic friendship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipArcWithCopper Context triple: [Young Tod, relationshipArcWithCopper, tragic friendship]
-
A.
cableMaterial
Indicates that one entity is the material from which the cable entity is made.
-
B.
associatedMetal
Indicates a relationship where one entity is linked or connected to a particular metal, such as by composition, usage, origin, or symbolic association.
-
C.
conductorType
Indicates the type or category of conductor involved in the relationship or action (e.g., material, role, or functional class).
-
D.
chainMadeOf
Indicates that a chain is composed of, or constructed from, a specified material or substance.
-
E.
plannedToBeConnectedTo
Indicates that one entity is intended or scheduled to be linked or joined with another entity in the future.
- 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:30 p.m.