Triple
T33660731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lydia Touchett |
E862343
|
entity |
| Predicate | bringsCharacterToEurope |
P76643
|
FINISHED |
| Object | Isabel Archer |
—
|
NE NERFINISHED |
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: Isabel Archer | Statement: [Lydia Touchett, bringsCharacterToEurope, Isabel Archer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bringsCharacterToEurope Context triple: [Lydia Touchett, bringsCharacterToEurope, Isabel Archer]
-
A.
arrivalInEurope
Indicates the event or state of something or someone reaching or entering a location within Europe.
-
B.
introducedToEuropeVia
chosen
Indicates that something was brought into and first became present in Europe through a particular source, route, or intermediary.
-
C.
enteredCombatInEurope
Indicates that an entity became actively involved in military combat operations within the geographical region of Europe.
-
D.
broughtToBritainBy
Indicates that something or someone was transported or introduced into Britain by a particular agent or source.
-
E.
roleInEurope
Indicates that an entity holds a specific function, position, or responsibility within a European context, such as within Europe as a region or its institutions.
- 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fa36f640819098051eff7e5a5787 |
completed | May 3, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:42 a.m.