Triple
T32234956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mulliner |
E823441
|
entity |
| Predicate | roleWithinBentley |
P173868
|
FINISHED |
| Object | flagship personalization arm |
—
|
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: flagship personalization arm | Statement: [Mulliner, roleWithinBentley, flagship personalization arm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleWithinBentley Context triple: [Mulliner, roleWithinBentley, flagship personalization arm]
-
A.
roleWithinBoeing
Indicates that one entity holds or has held a specific role, position, or function within the organization Boeing.
-
B.
roleWithinDaimler
Indicates that one entity holds or has held a specific role, position, or function within the Daimler organization.
-
C.
roleAtSiebelSystems
Indicates that an entity held a specific role or position at Siebel Systems.
-
D.
roleInBun
Indicates that an entity has a specific functional or contextual role within a particular bundle, grouping, or composite structure.
-
E.
roleWithinMBDA
Indicates the specific function, position, or responsibility an entity holds within the MBDA organizational or operational structure.
- 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbfe2bc88190a36ce3d7230d74a4 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:39 a.m.