Triple
T37049316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rescue of Jerry |
E917005
|
entity |
| Predicate | involvedPersonRole |
P184599
|
FINISHED |
| Object | fugitive slave |
—
|
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: fugitive slave | Statement: [Rescue of Jerry, involvedPersonRole, fugitive slave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedPersonRole Context triple: [Rescue of Jerry, involvedPersonRole, fugitive slave]
-
A.
involvesPartyRole
chosen
Indicates that a situation, event, or agreement includes a participant fulfilling a specific role or function within that context.
-
B.
namedPersonRole
Indicates that a person is identified by name as holding a specific role or position in a given context.
-
C.
roleOfPerson
Indicates that a specific role, function, or position is assigned to or held by a particular person.
-
D.
appliedToPersonRole
Indicates that something (such as a rule, condition, or action) is directed toward or relevant for a person specifically in their defined role or capacity.
-
E.
identificationRole
Indicates that an entity serves as an identifier or plays a role in uniquely distinguishing or recognizing 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
Created at: May 3, 2026, 4:14 p.m.