Triple
T7694070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Stranger (The Devil and Miss Prym) |
E174325
|
entity |
| Predicate | arrivesIn |
P49364
|
FINISHED |
| Object | a small village |
—
|
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: a small village | Statement: [the Stranger (The Devil and Miss Prym), arrivesIn, a small village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arrivesIn Context triple: [the Stranger (The Devil and Miss Prym), arrivesIn, a small village]
-
A.
arrivalAt
chosen
Indicates the event or state of an entity reaching and being present at a specific destination or location.
-
B.
estimatedArrivalInAustralia
Indicates the expected date and/or time when an entity is predicted to arrive in Australia.
-
C.
oftenArrivesBy
Indicates that one entity typically reaches or comes to another entity or location using a particular means or method.
-
D.
placeOfArrival
Indicates the location at which an entity or person arrives at the end of a journey, movement, or transfer.
-
E.
departsFrom
Indicates that an entity (such as a vehicle, person, or process) begins its movement, journey, or operation starting from a specified location or point of origin.
- 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_69c6995966348190939e6c37ba272c06 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c706d1f0208190bc5b695aa5736244 |
completed | March 27, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69c70163dea88190ae729df50e63dfd7 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:02 p.m.