Triple
T34055166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larga Distancia |
E873335
|
entity |
| Predicate | serviceFeatures |
P60612
|
FINISHED |
| Object | reserved seating |
—
|
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: reserved seating | Statement: [Larga Distancia, serviceFeatures, reserved seating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceFeatures Context triple: [Larga Distancia, serviceFeatures, reserved seating]
-
A.
featuresService
chosen
Indicates that one entity provides, includes, or offers a particular service as a notable characteristic or component.
-
B.
featuresSuit
Indicates that one entity includes or presents a particular suit (e.g., clothing, armor, or outfit) as a notable component or attribute.
-
C.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
D.
serviceCharacterization
Indicates how a service is defined, described, or classified in terms of its properties, behavior, or role.
-
E.
serviceBranchFeature
Indicates that a particular feature, capability, or characteristic is associated with or provided by a specific branch of service.
- 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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 1, 2026, 1:52 a.m.