Triple
T27790334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cueva de la Vaca |
E701060
|
entity |
| Predicate | typicalVisitorRequirement |
P12800
|
FINISHED |
| Object | accompanied by guide |
—
|
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: accompanied by guide | Statement: [Cueva de la Vaca, typicalVisitorRequirement, accompanied by guide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVisitorRequirement Context triple: [Cueva de la Vaca, typicalVisitorRequirement, accompanied by guide]
-
A.
visitorRequirement
chosen
Indicates the conditions or criteria that must be met by a visitor in order to be allowed or accepted.
-
B.
typicalVisitorBehavior
Indicates the usual or characteristic way visitors act, respond, or interact in a given context or environment.
-
C.
typicalRequirement
Indicates that one entity is a standard or commonly expected prerequisite, condition, or necessity for another entity.
-
D.
typicalVisitType
Indicates the usual or most common category of visit associated with an entity or event.
-
E.
boardingRequirement
Indicates the conditions or criteria that must be met for an entity to be allowed to board another entity (such as a vehicle, vessel, or aircraft).
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_6a00144238708190acbec3f791cc873e |
completed | May 10, 2026, 5:14 a.m. |
| PD | Predicate disambiguation | batch_6a00120244a4819090ef39070aba9d99 |
completed | May 10, 2026, 5:05 a.m. |
Created at: April 27, 2026, 5:27 p.m.