Triple
T16961152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Market Identifier Code |
E411429
|
entity |
| Predicate | dataModelRole |
P95292
|
FINISHED |
| Object | venue identifier |
—
|
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: venue identifier | Statement: [Market Identifier Code, dataModelRole, venue identifier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataModelRole Context triple: [Market Identifier Code, dataModelRole, venue identifier]
-
A.
dataModel
Indicates a relationship where an entity defines, uses, or is structured according to a specific data model or schema.
-
B.
associatedDataRole
chosen
Indicates that one entity has a specific role in relation to data that is linked or connected to another entity.
-
C.
roleModelFor
Indicates that one entity serves as an example or inspiration that another entity admires and seeks to emulate.
-
D.
visibilityRole
Indicates the role or level of access an entity has in determining what information or content is visible to others.
-
E.
roleInMetadata
Indicates that an entity serves a specific function or position within a metadata record or metadata structure.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0209a9081909d9c62456bc16e14 |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9cddf88190bc42709604047353 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.