Triple
T546861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiananmen Square |
E12750
|
entity |
| Predicate | touristVisits |
P12597
|
FINISHED |
| Object | millions of visitors per year |
—
|
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: millions of visitors per year | Statement: [Tiananmen Square, touristVisits, millions of visitors per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touristVisits Context triple: [Tiananmen Square, touristVisits, millions of visitors per year]
-
A.
touristArrivalsPerYearApprox
chosen
Indicates an approximate count of how many tourists arrive at a place over the course of a year.
-
B.
tourismRegion
Indicates that a place or area is designated or recognized as a tourism region associated with another geographic or administrative entity.
-
C.
tourismType
Indicates the specific category or kind of tourism activity or experience associated with an entity.
-
D.
isTouristDestination
Indicates that a place is recognized as a location people commonly visit for leisure, sightseeing, or travel.
-
E.
tourismImportance
Indicates the degree to which a place or entity is significant or valuable as a destination or attraction for tourists.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a498e150e88190b35b1bc7a376ca07 |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494b957988190bc269e372df2f0b2 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.