Triple
T29509507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porsche 924 |
E748608
|
entity |
| Predicate | layoutFamily |
P166983
|
FINISHED |
| Object | Porsche transaxle cars |
—
|
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: Porsche transaxle cars | Statement: [Porsche 924, layoutFamily, Porsche transaxle cars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layoutFamily Context triple: [Porsche 924, layoutFamily, Porsche transaxle cars]
-
A.
layoutCategory
Indicates how an entity is classified or grouped according to its layout or structural arrangement.
-
B.
layoutRole
Indicates how an entity functions or is positioned within a larger structural or spatial arrangement.
-
C.
layoutShape
Indicates a spatial or structural arrangement relationship where one entity defines or influences the geometric shape or configuration of another.
-
D.
layoutSupport
Indicates that one entity provides or enables structural or spatial arrangement capabilities for another entity.
-
E.
layoutEngine
Indicates the rendering or layout system responsible for arranging and positioning elements within a visual or document 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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c5d1cb48190867d8ce86724fb80 |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6642e676c8190af0e6b1416eed6d2 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 4:30 p.m.