Triple
T38261425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 42 Rio |
E1017937
|
entity |
| Predicate | admissionFeesRequired |
P3997
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [42 Rio, admissionFeesRequired, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admissionFeesRequired Context triple: [42 Rio, admissionFeesRequired, false]
-
A.
admissionFee
chosen
Indicates the monetary charge required for entry or participation in a place, event, or activity.
-
B.
admissionRequired
Indicates that access to something is conditional on being formally admitted or granted entry beforehand.
-
C.
hasTicketRequirement
Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
-
D.
separateAdmissionRequired
Indicates that access to this entity or activity is not covered by a general entry and requires an additional, distinct admission or ticket.
-
E.
isFreeStandingTicketRequired
Indicates whether a separate, stand-alone ticket is required for the related item or service.
- 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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.