Triple
T895071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reverend John Hale |
E19325
|
entity |
| Predicate | initialTrait |
P20799
|
FINISHED |
| Object | intellectually confident |
—
|
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: intellectually confident | Statement: [Reverend John Hale, initialTrait, intellectually confident]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialTrait Context triple: [Reverend John Hale, initialTrait, intellectually confident]
-
A.
initialReception
Indicates the nature or quality of the first response or reaction something receives when it is introduced or presented.
-
B.
firstToFeature
Indicates that one entity was the earliest or initial subject to exhibit, include, or present another entity in a given context.
-
C.
primaryCapability
Indicates that one entity serves as the main or most important functional ability, role, or competence of another entity.
-
D.
primaryTraction
Indicates that one entity serves as the main source or means of traction, pulling power, or driving force for another entity or process.
-
E.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad22b6fc819093e655c8ce1f738b |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa94f7c881908deeb62308942e19 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab4a38ec8190915916d80299ab55 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.