Triple
T31544890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isla Contoy |
E804847
|
entity |
| Predicate | visitorLimit |
P172576
|
FINISHED |
| Object | daily visitor number is restricted |
—
|
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: daily visitor number is restricted | Statement: [Isla Contoy, visitorLimit, daily visitor number is restricted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitorLimit Context triple: [Isla Contoy, visitorLimit, daily visitor number is restricted]
-
A.
visitorCount
Indicates the number of visitors associated with a particular entity, context, or time period.
-
B.
rideLimit
Indicates a constraint on the maximum number, duration, or frequency of rides permitted for an entity.
-
C.
visitorFrequency
Indicates how often a visitor comes to or interacts with a particular entity or location.
-
D.
visitorDemand
Indicates a relationship where the level or nature of demand expressed by visitors for something (e.g., a service, location, or resource) is specified or quantified.
-
E.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
- F. None of above. chosen
Provenance (4 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ac1ed23c8190ace57ffc9d8a3dc6 |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aba8fba48190bc1a17117244cae1 |
completed | May 3, 2026, 1:58 a.m. |
Created at: April 30, 2026, 10:07 p.m.