Triple
T20388239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pat (Green Room) |
E498013
|
entity |
| Predicate | survivalTheme |
P139934
|
FINISHED |
| Object | siege situation |
—
|
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: siege situation | Statement: [Pat (Green Room), survivalTheme, siege situation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivalTheme Context triple: [Pat (Green Room), survivalTheme, siege situation]
-
A.
survivorsJourney
Indicates the ongoing process or path a survivor takes as they cope with, adapt to, and move forward from a traumatic or life-threatening experience.
-
B.
survivesExpedition
Indicates that an entity endures and remains alive through the duration of a specified expedition or journey.
-
C.
helpsSurvive
Indicates that one entity provides support or advantage that increases another entity’s chances of survival.
-
D.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
E.
survivesShipwreck
Indicates that an entity continues to live or remain alive after experiencing a shipwreck.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6790d9e5881908bde7da9e5e541a0 |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:28 a.m.