Triple
T28143969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davy Crockett Explorer Canoes |
E714424
|
entity |
| Predicate | capacityPerCanoe |
P72527
|
FINISHED |
| Object | approximately 20 guests |
—
|
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: approximately 20 guests | Statement: [Davy Crockett Explorer Canoes, capacityPerCanoe, approximately 20 guests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capacityPerCanoe Context triple: [Davy Crockett Explorer Canoes, capacityPerCanoe, approximately 20 guests]
-
A.
hasBoatCapacity
chosen
Indicates the maximum number of people or amount of load that a boat is designed or allowed to carry.
-
B.
usesCanoes
Indicates that one entity makes use of canoes as a means of transport, activity, or operation in relation to another entity or context.
-
C.
lifeboatCapacity
Indicates the maximum number of people or load that a lifeboat is designed and certified to safely carry.
-
D.
canoeingVenue
Indicates that a location serves as a site or facility where canoeing activities take place.
-
E.
hasRaftingDifficulty
Indicates that an entity is associated with a specific level of rafting difficulty.
- 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_69efd6b033208190bf74f80a147e2092 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 9:55 p.m.