Triple
T2224892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Faithful Geyser of California |
E48625
|
entity |
| Predicate | requiresAdmissionFee |
P3997
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Old Faithful Geyser of California, requiresAdmissionFee, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresAdmissionFee Context triple: [Old Faithful Geyser of California, requiresAdmissionFee, yes]
-
A.
admissionFee
chosen
Indicates the monetary charge required for entry or participation in a place, event, or activity.
-
B.
hasTicketRequirement
Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
-
C.
isFreeToAttend
Indicates that attending the event or activity does not require any payment or admission fee.
-
D.
hasAdmission
Indicates that an entity possesses or is associated with a specific admission event, record, or status (such as being admitted to a place, program, or institution).
-
E.
requiresPaymentOf
Indicates that one entity obligates another entity to provide a specified payment as a condition or requirement.
- 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc03ec3788190b5ae32201364f7ab |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdac31d8819092d17815e11921e9 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.