Triple
T34562645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major General Thomas F. Waverly |
E887386
|
entity |
| Predicate | locationOfInn |
P89473
|
FINISHED |
| Object | Vermont |
E9978
|
NE 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: Vermont | Statement: [Major General Thomas F. Waverly, locationOfInn, Vermont]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfInn Context triple: [Major General Thomas F. Waverly, locationOfInn, Vermont]
-
A.
locationOfTavern
chosen
Indicates the relationship where a specified place serves as the location of a tavern.
-
B.
reservationLocatedIn
Indicates that a reservation (such as a booking or held resource) is situated within or associated with a specific location or place.
-
C.
reservationLocatedAlong
Indicates that a reservation is situated along, adjacent to, or following the course or extent of a specified linear feature such as a road, river, or boundary.
-
D.
locationFound
Indicates that a particular entity is located or discovered at a specific place or position.
-
E.
hallLocatedNear
Indicates that a hall is situated close to another specified place or entity in physical space.
- F. None of above.
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_69f349d0c4d881908dd0950f5eb9ec0a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3748dee6748190b38de1ccb99b34ca |
completed | June 21, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:02 a.m.