Triple
T32095913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pelóri Mountains |
E819720
|
entity |
| Predicate | builtUpBy |
P173804
|
FINISHED |
| Object | the Valar |
—
|
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: the Valar | Statement: [Pelóri Mountains, builtUpBy, the Valar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtUpBy Context triple: [Pelóri Mountains, builtUpBy, the Valar]
-
A.
builtFrom
Indicates that one entity is constructed, composed, or formed using another entity as its material, component, or source.
-
B.
builtThrough
Indicates that something was created, developed, or achieved by means of a specified method, process, or intermediary.
-
C.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
D.
wasBuilt
Indicates that one entity constructed, created, or assembled another entity, typically at a specific time or over a period.
-
E.
builtStructureFor
Indicates that one entity constructed or assembled a structure specifically intended for the use, benefit, or purpose of another entity.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba1733408190af579d93a7946508 |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:26 a.m.