Triple
T7075426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joseph Holt |
E164804
|
entity |
| Predicate | reasonForTransport |
P3057
|
FINISHED |
| Object | participation in the 1798 rebellion |
—
|
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: participation in the 1798 rebellion | Statement: [Joseph Holt, reasonForTransport, participation in the 1798 rebellion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForTransport Context triple: [Joseph Holt, reasonForTransport, participation in the 1798 rebellion]
-
A.
reasonForLocation
Indicates the cause, purpose, or justification for why an entity is at a particular location.
-
B.
reasonForRelocation
chosen
Indicates the underlying cause, motivation, or circumstance that led an entity to move from one location to another.
-
C.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
D.
causeOfChangeOfDestination
Indicates that one entity is the reason or trigger for another entity changing its intended destination.
-
E.
reasonForTime
Indicates that one entity provides the explanation or cause for a particular point or duration of time associated with another entity.
- 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_69c6887cbc6c8190bdfac42d940f4d8a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4ce3d3c81908cbb912b256aadbf |
completed | March 27, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:40 p.m.