Triple
T31036984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EAN International |
E790876
|
entity |
| Predicate | managedStandard |
P141716
|
FINISHED |
| Object | European Article Number |
—
|
NE NERFINISHED |
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: European Article Number | Statement: [EAN International, managedStandard, European Article Number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managedStandard Context triple: [EAN International, managedStandard, European Article Number]
-
A.
standardTypeManaged
chosen
Indicates that an entity is governed, controlled, or handled according to a defined standard type or classification.
-
B.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
-
C.
modeManaged
Indicates that one entity controls, configures, or oversees the operational mode or state of another entity.
-
D.
standardMaintained
Indicates that a specified standard is being upheld, preserved, or kept in compliance over time within the relevant context.
-
E.
managedAct
Indicates that one entity oversaw, directed, or was responsible for carrying out a particular action or activity.
- 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 29, 2026, 8:59 p.m.