Triple
T19784846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahimaaz |
E475233
|
entity |
| Predicate | volunteeredToRunWith |
P137321
|
FINISHED |
| Object | Cushite messenger |
—
|
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: Cushite messenger | Statement: [Ahimaaz, volunteeredToRunWith, Cushite messenger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: volunteeredToRunWith Context triple: [Ahimaaz, volunteeredToRunWith, Cushite messenger]
-
A.
volunteeredFor
Indicates that an entity willingly offered their time or services to support or participate in an activity, cause, or organization.
-
B.
volunteerRunLine
Indicates that a particular service, organization, or operation is managed and carried out primarily by volunteers rather than paid staff.
-
C.
runsTheLengthOf
Indicates that one entity extends continuously alongside or across the full distance of another entity.
-
D.
hasVolunteerParticipation
Indicates that an entity is involved in or benefits from activities performed by volunteers.
-
E.
studentRun
Indicates that an organization, activity, or initiative is operated and managed primarily by students rather than by faculty, staff, or external professionals.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6538715b8819080c6930e7d16ab58 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bcf41c8190b685b5adf46a60fc |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:49 p.m.