Triple
T8486715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Content-Language |
E200848
|
entity |
| Predicate | isEndToEnd |
P83552
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Content-Language, isEndToEnd, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEndToEnd Context triple: [Content-Language, isEndToEnd, true]
-
A.
isInterchangeBetween
Indicates a relationship where something serves as a point or medium through which two or more entities can exchange or transfer items, information, or traffic between each other.
-
B.
isInterchange
Indicates that two entities can be substituted or exchanged for one another without affecting the relevant system, function, or outcome.
-
C.
isFinalInstallmentOf
Indicates that one work or item is the concluding or last part in a series, sequence, or collection of related works.
-
D.
isInterchangeWith
Indicates that two entities can be substituted or exchanged for one another without loss of function, value, or compatibility.
-
E.
endOf
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
- 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe53c4d608190a766c0e919a4b96f |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe30c2d088190b4cb89adb4e88273 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:13 p.m.