Triple
T27790356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cueva de la Vaca |
E701060
|
entity |
| Predicate | typicalGroupActivity |
P164307
|
FINISHED |
| Object | team-based cave navigation |
—
|
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: team-based cave navigation | Statement: [Cueva de la Vaca, typicalGroupActivity, team-based cave navigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGroupActivity Context triple: [Cueva de la Vaca, typicalGroupActivity, team-based cave navigation]
-
A.
groupActing
chosen
Indicates that multiple entities are jointly performing or participating in the same action or activity as a group.
-
B.
typicalActivity
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
C.
activityType
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
-
D.
typicalGroup
Indicates that the subject belongs to or represents a standard, characteristic, or commonly occurring group associated with the object.
-
E.
schoolActivity
Indicates that an entity participates in, organizes, or is otherwise involved in an activity associated with a school or educational setting.
- 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_6a001540d4f881908a4688881875e774 |
completed | May 10, 2026, 5:18 a.m. |
| PD | Predicate disambiguation | batch_6a0014a8cdd88190a67a90a2df2c5e18 |
completed | May 10, 2026, 5:16 a.m. |
Created at: April 27, 2026, 5:27 p.m.