Triple
T6174154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buna |
E137776
|
entity |
| Predicate | hasConditions |
P1255
|
FINISHED |
| Object | starvation |
—
|
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: starvation | Statement: [Buna, hasConditions, starvation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConditions Context triple: [Buna, hasConditions, starvation]
-
A.
hasCondition
chosen
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
B.
hasNumberOfConditions
Indicates that an entity is associated with a specific count of conditions it has or is subject to.
-
C.
definesConditionsFor
Indicates that one entity specifies or establishes the rules, requirements, or circumstances under which another entity is valid, applicable, or operates.
-
D.
holdsUnderCondition
Indicates that one fact, rule, or relationship remains valid only when a specified condition or set of conditions is satisfied.
-
E.
hasPrecedingCondition
Indicates that one condition occurs or exists before another condition in time or sequence.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d94c47481909745b2533926a1ca |
completed | March 22, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.