Triple
T36271583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D-18 |
E892686
|
entity |
| Predicate | positionInLine |
P30257
|
FINISHED |
| Object | mahogany-bodied counterpart to D-28 |
—
|
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: mahogany-bodied counterpart to D-28 | Statement: [D-18, positionInLine, mahogany-bodied counterpart to D-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInLine Context triple: [D-18, positionInLine, mahogany-bodied counterpart to D-28]
-
A.
positionOnLine
Indicates that one entity occupies a specific location along a defined line or linear path in relation to another.
-
B.
positionInText
Indicates the specific location or span that something occupies within a text.
-
C.
positionInField
Indicates the specific role, location, or functional placement an entity occupies within a defined field, domain, or area of activity.
-
D.
positionInPage
Indicates the specific location or placement of an element within a page’s layout or structure.
-
E.
positionInProductLine
chosen
Indicates the specific place or order an item occupies within a defined product line or series.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff97637ad881908c24fe2cc6b036db |
completed | May 9, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69ff96c43a808190942eeda1934602db |
completed | May 9, 2026, 8:19 p.m. |
Created at: May 3, 2026, 4:09 p.m.