Triple
T4927835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saab Active Head Restraints (later models) |
E110619
|
entity |
| Predicate | targetBodyRegion |
P21283
|
FINISHED |
| Object | head |
—
|
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: head | Statement: [Saab Active Head Restraints (later models), targetBodyRegion, head]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetBodyRegion Context triple: [Saab Active Head Restraints (later models), targetBodyRegion, head]
-
A.
hasBodyRegion
chosen
Indicates that an entity possesses, includes, or is associated with a specific anatomical or bodily region.
-
B.
seatOfBody
Indicates that one entity serves as the physical location or base where another entity (typically an organization or authority) is situated or headquartered.
-
C.
bodyContour
Indicates the shape or outline of a body as defined by its external curves and boundaries.
-
D.
locatedOnBody
Indicates that one entity is physically situated on the surface or external part of another entity’s body.
-
E.
usesBodyPart
Indicates that an entity performs an action or function by employing a specific body part as a means or tool.
- 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_69bd4415190c8190817bee7ec9f9f944 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd7036d8e88190bc4be2975160da23 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3695c8819094e7ad2f6d4ba1ac |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.