Triple
T33269823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combahee River Raid |
E851745
|
entity |
| Predicate | commandRoleOfHarrietTubman |
P45245
|
FINISHED |
| Object | Scout and intelligence leader |
—
|
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: Scout and intelligence leader | Statement: [Combahee River Raid, commandRoleOfHarrietTubman, Scout and intelligence leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandRoleOfHarrietTubman Context triple: [Combahee River Raid, commandRoleOfHarrietTubman, Scout and intelligence leader]
-
A.
roleInHaiti
Indicates that an entity holds or held a specific role, position, or function within the context of Haiti.
-
B.
liberationRole
Indicates that an entity plays a specific role or function in the act or process of liberating or freeing another entity.
-
C.
economicRoleBeforeCivilWar
Indicates the economic function or position an entity held prior to the outbreak of the Civil War.
-
D.
roleInMissions
chosen
Indicates the specific function, duty, or position an entity holds within one or more missions.
-
E.
HarrisonRole
Indicates that an entity holds, has held, or is associated with a specific role or position in relation to Harrison.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 1, 2026, 1:32 a.m.