Triple
T16179119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HSV Clayton facility |
E392640
|
entity |
| Predicate | relationshipToHolden |
P122011
|
FINISHED |
| Object | specialist performance arm facility for Holden vehicles |
—
|
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: specialist performance arm facility for Holden vehicles | Statement: [HSV Clayton facility, relationshipToHolden, specialist performance arm facility for Holden vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToHolden Context triple: [HSV Clayton facility, relationshipToHolden, specialist performance arm facility for Holden vehicles]
-
A.
relationshipToHenry
Indicates the specific type of relationship or connection that an entity has to Henry.
-
B.
givesHolden
Indicates that one entity transfers or provides something to Holden.
-
C.
relationshipToHaydon
Indicates the specific type of personal or social relationship an entity has with Haydon.
-
D.
relationshipToHannah
Indicates the specific type of relationship or connection that an entity has to Hannah.
-
E.
relationshipToEvanHansen
Indicates the type or nature of a person's relationship or connection to Evan Hansen.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205b88b481908ecdd8d663dc668b |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:02 a.m.