Triple
T9381814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praia de Vilamoura |
E225802
|
entity |
| Predicate | commonVisitorNationalities |
P88628
|
FINISHED |
| Object | British 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: British tourists | Statement: [Praia de Vilamoura, commonVisitorNationalities, British tourists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonVisitorNationalities Context triple: [Praia de Vilamoura, commonVisitorNationalities, British tourists]
-
A.
onboardNationalities
Indicates the set of nationalities present among the people on board a given vehicle, vessel, or craft.
-
B.
bearerNationality
Indicates that one entity is the country or nationality associated with the bearer of another entity, such as a document or credential.
-
C.
hostNationality
Indicates the national affiliation or citizenship of the host in a given hosting relationship or context.
-
D.
nationalityInText
Indicates that a person's nationality is mentioned or specified within a given text.
-
E.
nationalityInHumanWorld
Indicates that one entity has the specified national affiliation or citizenship within the context of the human world.
- 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50be52248190bc7cd9deb95a1ef8 |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:44 p.m.