Triple
T11057002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Walker |
E261400
|
entity |
| Predicate | appealCalledFor |
P43136
|
FINISHED |
| Object | Black unity |
—
|
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: Black unity | Statement: [David Walker, appealCalledFor, Black unity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appealCalledFor Context triple: [David Walker, appealCalledFor, Black unity]
-
A.
hasAppealsTo
Indicates that one entity formally challenges or seeks review of a decision, judgment, or outcome through another entity or process.
-
B.
appealStatus
Indicates the current state or outcome of an appeal within a review or decision process.
-
C.
appealsFor
chosen
Indicates that one entity formally requests support, intervention, or a favorable decision from another entity.
-
D.
appeal
Indicates that one party formally requests a higher authority to review, reconsider, or overturn a prior decision, judgment, or outcome.
-
E.
canBeAppealedTo
Indicates that a decision, action, or authority is subject to being challenged or reviewed by a higher or alternative authority through an appeal process.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798a2404c819090cb0825a67a64fa |
completed | April 9, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.