Triple
T2202044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Test Baker |
E50510
|
entity |
| Predicate | falloutType |
P36941
|
FINISHED |
| Object | base surge laden with radioactive water droplets |
—
|
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: base surge laden with radioactive water droplets | Statement: [Test Baker, falloutType, base surge laden with radioactive water droplets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: falloutType Context triple: [Test Baker, falloutType, base surge laden with radioactive water droplets]
-
A.
deathTerritory
Indicates the territory or geographic area where a death occurred or is officially recorded.
-
B.
fellOn
Indicates that one entity moved downward, typically due to gravity, and came to rest on the surface of another entity.
-
C.
fate
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
-
D.
fallsIn
Indicates that one entity is located within, contained by, or geographically/administratively included inside another entity.
-
E.
usedWarfareType
Indicates the specific type or method of warfare that an entity employed in a conflict or military context.
- 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfa1b41c8190b0f7467d0dcdfbcd |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda706f4819094de73e1d1d1f539 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf35c994819088a093c412931de4 |
completed | March 7, 2026, 6:01 a.m. |
Created at: March 4, 2026, 7:46 p.m.