Triple
T11613769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humility Cooper |
E275450
|
entity |
| Predicate | traveledAs |
P100605
|
FINISHED |
| Object | ward |
—
|
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: ward | Statement: [Humility Cooper, traveledAs, ward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traveledAs Context triple: [Humility Cooper, traveledAs, ward]
-
A.
traveledFor
Indicates that an entity moved or journeyed to a place or event for a specific purpose, reason, or activity.
-
B.
traveledToBy
Indicates that an entity has been traveled to or visited by another entity.
-
C.
travelsOn
Indicates that an entity moves or journeys using a particular route, path, or mode of transportation.
-
D.
isFlownOn
Indicates that an entity (such as a person or object) travels or is transported using a particular aircraft or airline as the means of flight.
-
E.
involvedTravelBetween
Indicates a relationship where an entity participates in or is associated with travel occurring between two specified locations.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a044a3088190b92f4674c2d0b443 |
completed | April 10, 2026, 7:01 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:38 p.m.