Triple
T37508506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humbling the Proud |
E932156
|
entity |
| Predicate | targetSin |
P199451
|
FINISHED |
| Object | hubris |
—
|
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: hubris | Statement: [Humbling the Proud, targetSin, hubris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetSin Context triple: [Humbling the Proud, targetSin, hubris]
-
A.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
B.
targetSide
Indicates the specific side or aspect of a referenced target that is involved in or affected by the relationship or action.
-
C.
targetUnit
Indicates that one entity serves as the specific unit or object that another entity is directed at, operates on, or is intended to affect.
-
D.
targetsVector
Indicates that one entity is directed toward, aimed at, or focused on another entity represented as a vector (e.g., a direction or target position).
-
E.
targetsSource
Indicates that something is directed at, aimed toward, or focused on a specified source as its primary origin or object.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff397e19a88190a945b826159f5290 |
completed | May 9, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69ff392400d0819088d30d08d4a774bd |
completed | May 9, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_69ff397d6a2081908fa8f62e8902421b |
completed | May 9, 2026, 1:41 p.m. |
Created at: May 3, 2026, 4:17 p.m.