Triple
T30318290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Partage de midi |
E771116
|
entity |
| Predicate | revisedVersionCompletedInYear |
P145834
|
FINISHED |
| Object | 1948 |
—
|
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: 1948 | Statement: [Partage de midi, revisedVersionCompletedInYear, 1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revisedVersionCompletedInYear Context triple: [Partage de midi, revisedVersionCompletedInYear, 1948]
-
A.
revisedVersionCompletion
Indicates that one entity represents the completed or finalized form of a revised version of another entity.
-
B.
revisionCompletionYear
chosen
Indicates the year in which a revision of something (e.g., a work, document, or item) was completed.
-
C.
dateRevisedTo
Indicates that an entity’s date has been updated or changed to a new specified date.
-
D.
finalVersionYear
Indicates the year in which the final or last version of something was completed, released, or became definitive.
-
E.
revisedVersionType
Indicates that one entity is a revised form of another, specifying the type or nature of the revision made.
- 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_69f22489ee8481909344649bfbb92e83 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68195fcfc8190b6d3ee313c734f60 |
completed | May 2, 2026, 10:58 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:51 p.m.