Triple
T23289128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuma Tent |
E589976
|
entity |
| Predicate | distinctionFromSaharaTent |
P151719
|
FINISHED |
| Object | more intimate and club-oriented |
—
|
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: more intimate and club-oriented | Statement: [Yuma Tent, distinctionFromSaharaTent, more intimate and club-oriented]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distinctionFromSaharaTent Context triple: [Yuma Tent, distinctionFromSaharaTent, more intimate and club-oriented]
-
A.
desertsFrom
Indicates that an entity abandons or leaves allegiance to another entity, typically in a disloyal or unauthorized manner.
-
B.
hasNearbyDesert
Indicates that one entity is located close to or in the vicinity of a desert region associated with another entity.
-
C.
hasDesertType
Indicates that an entity is characterized by or associated with a specific type or category of desert.
-
D.
isLocatedInDesert
Indicates that something exists or is situated within a desert region or environment.
-
E.
traversesDesert
Indicates that an entity moves across or through a desert region, typically implying a journey over arid terrain.
- 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_69e25d1af9d88190a0b9b5e8fa608618 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19649570c8190b565fafa55b1f886 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 5:01 p.m.