Triple
T16142669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rim Fire |
E391699
|
entity |
| Predicate | fullContainmentPercentage |
P121273
|
FINISHED |
| Object | 100% |
—
|
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: 100% | Statement: [Rim Fire, fullContainmentPercentage, 100%]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullContainmentPercentage Context triple: [Rim Fire, fullContainmentPercentage, 100%]
-
A.
containedWith
Indicates that one entity is located or kept inside the bounds or interior space of another entity.
-
B.
hasContainment
Indicates that one entity spatially or logically encloses, includes, or holds another within its bounds.
-
C.
containsMostOf
Indicates that one entity includes the majority (but not necessarily all) of the substance, elements, or components of another entity.
-
D.
alsoContains
Indicates that something includes, in addition to its primary contents, another specified element or component.
-
E.
typicallyContain
Indicates that one entity is normally or commonly found within, included in, or held by another entity under usual circumstances.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21d9082588190bc7e6ff491f0d94e |
completed | April 17, 2026, 11:46 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e1835b64948190ae1d2a9d4cc64acf |
completed | April 17, 2026, 12:48 a.m. |
Created at: April 10, 2026, 5:01 a.m.