Triple
T33744571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Brothers |
E864663
|
entity |
| Predicate | middlePeak |
P76598
|
FINISHED |
| Object | Middle Brother |
—
|
NE NERFINISHED |
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: Middle Brother | Statement: [Three Brothers, middlePeak, Middle Brother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: middlePeak Context triple: [Three Brothers, middlePeak, Middle Brother]
-
A.
centralPeak
chosen
Indicates that one entity is the central, elevated peak located near the middle of another entity, typically within a larger structure such as a crater or basin.
-
B.
isEasternPeakOf
Indicates that one peak is the eastern member or counterpart within a set or pair of related peaks.
-
C.
otherMajorPeak
Indicates that one peak is another significant or prominent peak associated with, but distinct from, a given primary peak.
-
D.
isCentralPeakOf
Indicates that one entity is the main, elevated peak located near the center of another, typically larger, geological or impact structure.
-
E.
moreProminentSummit
Indicates that one summit is higher, more notable, or more significant than another in terms of prominence.
- 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb5d436c8190a37a1cc8001319ac |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:44 a.m.