Triple
T20394951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soberanes Fire |
E500176
|
entity |
| Predicate | fullContainmentDate |
P139971
|
FINISHED |
| Object | 2016-10-12 |
—
|
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: 2016-10-12 | Statement: [Soberanes Fire, fullContainmentDate, 2016-10-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullContainmentDate Context triple: [Soberanes Fire, fullContainmentDate, 2016-10-12]
-
A.
complianceDateForMostCoveredEntities
Indicates the date by which the majority of entities subject to a given rule or requirement must achieve compliance.
-
B.
fullOperationDate
Indicates the date on which an operation or process is fully carried out or becomes completely effective.
-
C.
enclosedSince
Indicates that one entity has been contained or surrounded by another entity continuously starting from a specified point in time.
-
D.
holdingDate
Indicates the date on which a holding, possession, or ownership of something is recorded or takes effect.
-
E.
fullContainmentPercentage
Indicates the proportion of one entity that is completely contained within another, expressed as a percentage.
- 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_69e679122058819083e3615a5ea0a82e |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 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.