Triple
T38566455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minas Tirith of Finrod |
E928231
|
entity |
| Predicate | originalLord |
P128624
|
FINISHED |
| Object | Finrod Felagund |
E891114
|
NE 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: Finrod Felagund | Statement: [Minas Tirith of Finrod, originalLord, Finrod Felagund]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalLord Context triple: [Minas Tirith of Finrod, originalLord, Finrod Felagund]
-
A.
lordOf
Indicates that one entity holds lordship, authority, or dominion over another entity.
-
B.
firstKnownLord
chosen
Indicates that the subject is the earliest historically or canonically recorded lord associated with the object.
-
C.
laterLordHouse
Indicates that one entity serves as the later or subsequent lordly house associated with another entity, typically in a succession or lineage of houses.
-
D.
borderLord
Indicates that one entity serves as the feudal or territorial lord presiding over a border or frontier region associated with another entity.
-
E.
originalFor
Indicates that one entity serves as the source, basis, or prototype from which another entity is derived, adapted, or created.
- F. None of above.
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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a5ba039e3a081908ac5c3a44928709b |
completed | July 18, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.