Triple
T25100959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | wali |
E628718
|
entity |
| Predicate | recognizedCriterion |
P159074
|
FINISHED |
| Object | steadfast faith |
—
|
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: steadfast faith | Statement: [wali, recognizedCriterion, steadfast faith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedCriterion Context triple: [wali, recognizedCriterion, steadfast faith]
-
A.
recognizedFeature
Indicates that a particular feature has been identified and acknowledged as present or valid in relation to an entity or context.
-
B.
recognizedSee
Indicates that one entity sees another and consciously recognizes or identifies what is being seen.
-
C.
recognizedFor
Indicates that one entity is acknowledged, credited, or honored for a particular achievement, quality, contribution, or work associated with another entity.
-
D.
proposesCriterion
Indicates that one entity suggests or puts forward a specific criterion to be considered or used by another entity or within a given context.
-
E.
compositionCriterion
Indicates the rule or standard by which components are selected, combined, or arranged to form a whole.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 18, 2026, 6:25 a.m.