Triple
T29966685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IT-MOL |
E761200
|
entity |
| Predicate | hasOfficialUseBy |
P24110
|
FINISHED |
| Object | European Commission |
—
|
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 Commission | Statement: [IT-MOL, hasOfficialUseBy, European Commission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialUseBy Context triple: [IT-MOL, hasOfficialUseBy, European Commission]
-
A.
hasOfficialUse
chosen
Indicates that something is used in an authorized or formally recognized capacity, typically by an official body or for official purposes.
-
B.
hasOfficial
Indicates that an entity is formally associated with, represented by, or served by a designated official or office-holder.
-
C.
usedInOfficialDocumentsOf
Indicates that something (e.g., a term, symbol, or format) is employed within the formal or legally recognized documents issued by a particular entity or jurisdiction.
-
D.
isOfficial
Indicates that an entity holds formal, authorized, or government-recognized status in a given context.
-
E.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
- 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_69f22466327481908ba6db916837bece |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 29, 2026, 6:30 p.m.