Triple
T16266655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statue City Cruises |
E394891
|
entity |
| Predicate | offersServiceFeature |
P9404
|
FINISHED |
| Object | timed entry reservations |
—
|
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: timed entry reservations | Statement: [Statue City Cruises, offersServiceFeature, timed entry reservations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersServiceFeature Context triple: [Statue City Cruises, offersServiceFeature, timed entry reservations]
-
A.
offersFeature
chosen
Indicates that one entity provides or makes available a particular feature or capability to another entity.
-
B.
offersServiceIn
Indicates that a provider makes a particular service available within a specified location or jurisdiction.
-
C.
offersServiceTo
Indicates that one entity provides or makes a service available for the benefit or use of another entity.
-
D.
offersServiceType
Indicates that one entity provides or makes available a specific type or category of service to another entity or the public.
-
E.
offersServiceOn
Indicates that one entity provides or makes a service available on, during, or through another entity (such as a platform, date, or location).
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c839788190b974d1d0d2525b88 |
completed | April 17, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:05 a.m.