Triple
T20221630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edna |
E495268
|
entity |
| Predicate | visitType |
P91146
|
FINISHED |
| Object | unexpected visit |
—
|
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: unexpected visit | Statement: [Edna, visitType, unexpected visit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitType Context triple: [Edna, visitType, unexpected visit]
-
A.
visitorPractice
Indicates that a visitor engages in or performs a particular practice, activity, or routine.
-
B.
visitorIs
Indicates that one entity is acting in the role or capacity of a visitor with respect to another entity.
-
C.
visitorStatus
Indicates the current state or condition of an entity in its role as a visitor (e.g., whether they are active, pending, past, or otherwise classified in their visit).
-
D.
visitorService
Indicates a relationship where a service is provided specifically for or to visitors, such as assistance, information, or support during their visit.
-
E.
typicalVisitType
chosen
Indicates the usual or most common category of visit associated with an entity or event.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd610f881908fdd22b1f8bd2efc |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.