Triple
T15466513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Wario |
E372042
|
entity |
| Predicate | section3Feature |
P38807
|
FINISHED |
| Object | dam interior |
—
|
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: dam interior | Statement: [Mount Wario, section3Feature, dam interior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: section3Feature Context triple: [Mount Wario, section3Feature, dam interior]
-
A.
section3ContentSummary
Indicates a summarized representation of the main points or key information contained in the third section of a document or structure.
-
B.
section3Effect
Indicates the effect, consequence, or outcome that arises specifically from the application or enforcement of section 3 of a given law, policy, or document.
-
C.
featuresSegment
chosen
Indicates that one entity includes or highlights a particular segment or portion of another entity as a notable part of it.
-
D.
section2Description
Indicates the descriptive text or content provided for the second section of a structured item or document.
-
E.
section5Description
Indicates a descriptive text or explanation specifically associated with section 5 of a document or structured content.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f680cec8190836a5ec841dee224 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:33 a.m.