Triple
T29023346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bynum Walker |
E737514
|
entity |
| Predicate | guidesProcess |
P18444
|
FINISHED |
| Object | self-discovery |
—
|
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: self-discovery | Statement: [Bynum Walker, guidesProcess, self-discovery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guidesProcess Context triple: [Bynum Walker, guidesProcess, self-discovery]
-
A.
hasGuides
Indicates that an entity is associated with one or more guides that provide direction, instruction, or assistance.
-
B.
guidesAfterEvent
Indicates that one entity provides guidance or direction to another entity following a specific event or occurrence.
-
C.
documentedProcess
Indicates that a process has been formally recorded, described, or specified in documentation.
-
D.
providesGuidanceTo
chosen
Indicates that one entity offers direction, advice, or instruction to another entity.
-
E.
typicalProcess
Indicates that the related process is characteristic, usual, or commonly occurring for the given entity or context.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66007a5d8819085fcc6651a89a189 |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:50 a.m.