Triple
T13657985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reblochon |
E326910
|
entity |
| Predicate | AOPStatusGranted |
P50587
|
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: [Reblochon, AOPStatusGranted, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AOPStatusGranted Context triple: [Reblochon, AOPStatusGranted, 1996]
-
A.
grantedStatus
Indicates that an entity has been officially approved or given a particular status, permission, or privilege.
-
B.
statusGrantedOn
chosen
Indicates the date or time at which a particular status was officially conferred or became effective for an entity.
-
C.
hasAuthorityStatus
Indicates that one entity holds a particular level or type of official power, control, or decision-making authority over another entity or within a defined context.
-
D.
mintStatusGranted
Indicates that an entity has been officially authorized or approved to mint (create or issue) something, such as tokens, assets, or items.
-
E.
authorityGranted
Indicates that one entity has formally given another entity the power, rights, or permission to act or make decisions, typically within a defined scope or context.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc61f0d808190b1cd2a6ba0d930eb |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:52 p.m.