Triple
T23336394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capet |
E591596
|
entity |
| Predicate | endOfDirectLine |
P48547
|
FINISHED |
| Object | 1328 |
—
|
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: 1328 | Statement: [Capet, endOfDirectLine, 1328]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfDirectLine Context triple: [Capet, endOfDirectLine, 1328]
-
A.
officeEnded
Indicates that a person’s term in an office or position has concluded at a specified time or under certain conditions.
-
B.
endOf
chosen
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
C.
serviceEnded
Indicates that a previously active service or service relationship has come to an end.
-
D.
closedAsLinearChannel
Indicates that one entity has been closed or terminated by being converted into or treated as a linear (one-way, sequential) communication channel.
-
E.
endLineUsage
Indicates the relationship where a particular line or resource is used up to or at its terminating point or final extent.
- 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197f1e0588190bf073b92be0bf9e4 |
completed | April 29, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:16 p.m.