Triple
T6397745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pli selon pli |
E143981
|
entity |
| Predicate | firstVersionCompleted |
P51515
|
FINISHED |
| Object | 1960 |
—
|
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: 1960 | Statement: [Pli selon pli, firstVersionCompleted, 1960]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstVersionCompleted Context triple: [Pli selon pli, firstVersionCompleted, 1960]
-
A.
firstReleaseVersion
Indicates the specific version identifier associated with the initial public release of something.
-
B.
firstFullVersionReference
Indicates that one entity serves as the initial complete or fully realized version to which another entity refers or is linked.
-
C.
firstRelease
Indicates that one entity is the initial or earliest release (in time or sequence) of another entity, such as a product, work, or version.
-
D.
laterCompletionVersion
Indicates that one entity is a version of a completion that occurs or is produced later in time than another related version.
-
E.
firstVersionYear
chosen
Indicates the calendar year in which the first version or initial release of something was created, published, or made available.
- 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_69c008dc56fc81908d43ffcc11d73bdd |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06896d180819091548a728e903184 |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f25c088190b433f78553ff1d84 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:35 p.m.