Triple
T19251776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langres cheese |
E481408
|
entity |
| Predicate | hasAOPStatusSince |
P40610
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Langres cheese, hasAOPStatusSince, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAOPStatusSince Context triple: [Langres cheese, hasAOPStatusSince, 1996]
-
A.
hasVersionStatus
Indicates that an entity is associated with a particular version state or status within its lifecycle or revision history.
-
B.
hasStatusBasedOn
Indicates that an entity’s status is determined or derived from another condition, event, or entity.
-
C.
hasAdministrativeStatusSince
chosen
Indicates that an entity has held a particular administrative status continuously from a specified point in time onward.
-
D.
hasClockSince
Indicates that an entity has possessed or maintained a clock continuously from a specified point in time onward.
-
E.
hasHistorySince
Indicates that an entity has maintained a particular state, condition, or relationship continuously starting from a specified point in time.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb30bf6c819094c44aceb544a023 |
completed | April 20, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:28 p.m.