Triple
T13180313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlina |
E313704
|
entity |
| Predicate | relativeToBaseModel |
P99027
|
FINISHED |
| Object | offers upgraded comfort over base Holden Commodore |
—
|
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: offers upgraded comfort over base Holden Commodore | Statement: [Berlina, relativeToBaseModel, offers upgraded comfort over base Holden Commodore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeToBaseModel Context triple: [Berlina, relativeToBaseModel, offers upgraded comfort over base Holden Commodore]
-
A.
associatedBase
Indicates a relationship where one entity is linked or connected to a corresponding base entity that it depends on or is derived from.
-
B.
relationshipToOriginalStructure
chosen
Indicates the nature or degree of connection that something has to its initial or source structure.
-
C.
associatedBaseName
Indicates that one entity is linked to or derived from another entity’s base or canonical name.
-
D.
isRelativeTo
Indicates that one entity has a familial or kinship relationship to another entity.
-
E.
relativeToIonic
Indicates a relationship defined in comparison or reference to an ionic state, property, or standard.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:14 p.m.