Triple
T4640612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Deep |
E101644
|
entity |
| Predicate | hasApproximateAnnualVisitors |
P12597
|
FINISHED |
| Object | hundreds of thousands |
—
|
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: hundreds of thousands | Statement: [The Deep, hasApproximateAnnualVisitors, hundreds of thousands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateAnnualVisitors Context triple: [The Deep, hasApproximateAnnualVisitors, hundreds of thousands]
-
A.
touristArrivalsPerYearApprox
chosen
Indicates an approximate count of how many tourists arrive at a place over the course of a year.
-
B.
visitorFrequency
Indicates how often a visitor comes to or interacts with a particular entity or location.
-
C.
visitorCount
Indicates the number of visitors associated with a particular entity, context, or time period.
-
D.
annualVisitation
Indicates a recurring visit or attendance that takes place once every year between the related entities.
-
E.
hasAnnualPassengerTrafficOver
Indicates that the subject location or transport facility experiences an annual passenger volume exceeding a specified threshold.
- 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_69bd43d3bc7c81908f81fcf380476b0f |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a8fbd2c8190b593cd46ce8dfe0f |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5234d24c819095c79890b70eff9a |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:14 p.m.