Triple
T28900219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DIN 41612 |
E732931
|
entity |
| Predicate | hasContactTermination |
P201605
|
FINISHED |
| Object | solder tail |
—
|
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: solder tail | Statement: [DIN 41612, hasContactTermination, solder tail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContactTermination Context triple: [DIN 41612, hasContactTermination, solder tail]
-
A.
hasContactState
Indicates that an entity is currently in a specific state or condition regarding its physical or communicative contact with another entity.
-
B.
wasTerminated
Indicates that an entity’s employment, contract, or ongoing role was ended, typically by a decision from another party rather than by the entity itself.
-
C.
typicallyTerminatedIn
Indicates that an event, process, or state usually ends or concludes in a particular way or outcome.
-
D.
canTerminate
Indicates that one entity has the authority or ability to end or discontinue another entity, process, or relationship.
-
E.
hasContactType
Indicates the specific kind or category of contact relationship that exists between two entities.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a000be59ad88190a6aa3a42c097796d |
completed | May 10, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_6a000ab6e9bc81908300b81d004e5921 |
completed | May 10, 2026, 4:33 a.m. |
| PDg | Predicate description generation | batch_6a000be4d3f48190bdecd0a044a0e453 |
completed | May 10, 2026, 4:39 a.m. |
Created at: April 28, 2026, 8:02 a.m.