Triple
T38566453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minas Tirith of Finrod |
E928231
|
entity |
| Predicate | builtOnFeature |
P2012
|
FINISHED |
| Object | island in the River Sirion |
—
|
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: island in the River Sirion | Statement: [Minas Tirith of Finrod, builtOnFeature, island in the River Sirion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtOnFeature Context triple: [Minas Tirith of Finrod, builtOnFeature, island in the River Sirion]
-
A.
builtOn
chosen
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
B.
builtUpBy
Indicates that something has been constructed, developed, or formed through the actions or contributions of a specified agent or process.
-
C.
builtThrough
Indicates that something was created, developed, or achieved by means of a specified method, process, or intermediary.
-
D.
builtFrom
Indicates that one entity is constructed, composed, or formed using another entity as its material, component, or source.
-
E.
builtType
Indicates the structural or construction type characterizing how something is built or formed.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.