Triple
T28079019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baby Beach |
E709623
|
entity |
| Predicate | hasCommonVisitorOrigin |
P74830
|
FINISHED |
| Object | international tourists |
—
|
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: international tourists | Statement: [Baby Beach, hasCommonVisitorOrigin, international tourists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonVisitorOrigin Context triple: [Baby Beach, hasCommonVisitorOrigin, international tourists]
-
A.
hasPrimaryVisitorOrigin
Indicates that an entity’s main or most common source location of its visitors is a specified place.
-
B.
hasCommonVisitor
Indicates that two entities share at least one visitor in common.
-
C.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
D.
hasUnspecifiedOrigin
Indicates that the origin or source of the related entity is unknown, undefined, or not specifically identified.
-
E.
typicalVisitorOrigin
chosen
Indicates the usual geographic source or location from which visitors to a place, event, or entity most commonly come.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
Created at: April 27, 2026, 8:50 p.m.