Triple
T32095871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alqualondë |
E819719
|
entity |
| Predicate | associatedWithKindred |
P7844
|
FINISHED |
| Object | Lindar |
E1953662
|
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: Lindar | Statement: [Alqualondë, associatedWithKindred, Lindar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithKindred Context triple: [Alqualondë, associatedWithKindred, Lindar]
-
A.
associatedHeir
Indicates that one entity is designated or recognized as the heir connected to, or inheriting from, another entity.
-
B.
associatedWithPatriarch
Indicates that an entity has a relationship, connection, or affiliation with a patriarch, such as being under their authority, influence, or domain.
-
C.
associatedWithParents
Indicates a relationship where an entity is linked or connected to its parents in some relevant context.
-
D.
hasFamilialTieTo
chosen
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
E.
associatedWithHeirApparent
Indicates a relationship in which an entity is connected or linked to a designated heir apparent, typically through role, status, or relevant association.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f0120104c81909ae32358ff3f241f |
completed | June 14, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:26 a.m.