Triple
T26377859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OEM |
E660946
|
entity |
| Predicate | exampleRole |
P164834
|
FINISHED |
| Object | car maker integrating advanced driver‑assistance systems |
—
|
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: car maker integrating advanced driver‑assistance systems | Statement: [OEM, exampleRole, car maker integrating advanced driver‑assistance systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exampleRole Context triple: [OEM, exampleRole, car maker integrating advanced driver‑assistance systems]
-
A.
testRole
Indicates that an entity is assigned or associated with a specific role used for testing or validation purposes.
-
B.
ClientRole
Indicates that an entity participates in a relationship or interaction specifically in the capacity of a client.
-
C.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
-
D.
profileRole
Indicates the specific role or function an entity holds within a given profile or contextual configuration.
-
E.
eraRole
Indicates the specific role, function, or capacity an entity has within a particular historical or temporal era.
- F. None of above. chosen
Provenance (4 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f650fc44e48190bc0e0a935eac62a6 |
completed | May 2, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f650c466b881908954e43bfebae8a4 |
completed | May 2, 2026, 7:30 p.m. |
Created at: April 26, 2026, 11:02 p.m.