Triple
T29999033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Front Row |
E762109
|
entity |
| Predicate | designedForUseDistance |
P192775
|
FINISHED |
| Object | living room viewing |
—
|
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: living room viewing | Statement: [Front Row, designedForUseDistance, living room viewing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForUseDistance Context triple: [Front Row, designedForUseDistance, living room viewing]
-
A.
downrangeDistance_km
Indicates the horizontal distance, measured in kilometers, that an object has traveled along its ground track from a defined launch or reference point.
-
B.
supportsTransmissionDistance
Indicates that one entity enables or is compatible with the transmission of signals or data over a specified distance.
-
C.
lengthInKm
Indicates that one entity specifies the length or distance of another entity measured in kilometers.
-
D.
hasDistanceCategory
Indicates that one entity is associated with a qualitative or categorical classification of its distance relative to another entity or reference point.
-
E.
trackLengthApproxKm
Indicates that one entity has an approximate track length, measured in kilometers, associated with it.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
| PDg | Predicate description generation | batch_69fd2a2095f88190bfcbcb2973516ffc |
completed | May 8, 2026, 12:11 a.m. |
Created at: April 29, 2026, 6:40 p.m.