Triple
T8242664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stan Uris |
E192773
|
entity |
| Predicate | definingStruggle |
P40613
|
FINISHED |
| Object | fear |
—
|
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: fear | Statement: [Stan Uris, definingStruggle, fear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definingStruggle Context triple: [Stan Uris, definingStruggle, fear]
-
A.
struggleFor
Indicates a relationship where one entity exerts effort or engages in conflict in order to obtain, achieve, or defend another entity or goal.
-
B.
meansOfStruggle
Indicates the method, tactic, or form of action used by an entity in carrying out a struggle or conflict.
-
C.
associatedWithStruggle
chosen
Indicates a relationship in which an entity is connected to, involved in, or characterized by a particular struggle, conflict, or hardship.
-
D.
armedStruggleAgainst
Indicates an organized, often violent resistance or conflict carried out by one party using weapons against another party, typically to oppose or overthrow its control or policies.
-
E.
notableStruggles
Indicates that the subject has faced significant challenges, difficulties, or adversities that are especially noteworthy or defining.
- 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb786f65708190a92ec282b280c813 |
completed | March 31, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:47 p.m.