Triple
T36672824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gatteo a Mare |
E905463
|
entity |
| Predicate | hasTargetTourists |
P125658
|
FINISHED |
| Object | families with children |
—
|
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: families with children | Statement: [Gatteo a Mare, hasTargetTourists, families with children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTargetTourists Context triple: [Gatteo a Mare, hasTargetTourists, families with children]
-
A.
hasTouristVisits
Indicates that one entity experiences or records visits from tourists to another entity.
-
B.
hasTouristPopularity
Indicates that a place or attraction is recognized as being popular or frequently visited by tourists.
-
C.
hasTouristProfile
Indicates that an entity possesses characteristics, data, or attributes defining it as a tourist or related to tourism behavior.
-
D.
hasGoalForTourists
Indicates that something is intended or designed to achieve a specific objective or benefit for tourists.
-
E.
hasTargetVisitors
chosen
Indicates that something is intended or designed to be visited by a specific group of people as its primary audience or users.
- 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.