Triple
T36074804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H247 |
E1043469
|
entity |
| Predicate | internalCodeFor |
P108285
|
FINISHED |
| Object | second-generation Mercedes-Benz GLA |
—
|
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: second-generation Mercedes-Benz GLA | Statement: [H247, internalCodeFor, second-generation Mercedes-Benz GLA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internalCodeFor Context triple: [H247, internalCodeFor, second-generation Mercedes-Benz GLA]
-
A.
internalCode
chosen
Indicates that an entity is associated with an internal identification code used within a specific system or organization.
-
B.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
C.
codeForSystem
Indicates that something serves as the code, identifier, or encoding used within or by a particular system.
-
D.
isOfficialCodeFor
Indicates that one entity serves as the formally recognized or authorized code that designates or identifies another entity.
-
E.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
Created at: May 3, 2026, 4:08 p.m.