Triple
T8262752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calle San Sebastián |
E193230
|
entity |
| Predicate | hasCommonVisitor |
P81566
|
FINISHED |
| Object | local residents |
—
|
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: local residents | Statement: [Calle San Sebastián, hasCommonVisitor, local residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonVisitor Context triple: [Calle San Sebastián, hasCommonVisitor, local residents]
-
A.
hasVisitorFunction
Indicates that an entity is associated with a function or method that implements the Visitor pattern to operate on it.
-
B.
hasVisitorType
Indicates the type or category of visitor associated with an entity (e.g., guest, customer, tourist, patient).
-
C.
hasVisitorBuilding
Indicates that a particular building serves as a designated visitor facility or is intended for use by visitors.
-
D.
hasVisitorsFrom
Indicates that an entity receives or has received visitors originating from another specified entity or location.
-
E.
hasVisitorServices
Indicates that an entity provides services or facilities specifically intended for visitors or guests.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7938723081909379cf78a4449b80 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb36b8707881909aca349230495a5a |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb4ab5162c8190bddd696078689895 |
completed | March 31, 2026, 4:16 a.m. |
Created at: March 30, 2026, 5:49 p.m.