Triple
T37142576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nenning |
E920154
|
entity |
| Predicate | associatedWithLord |
P205757
|
FINISHED |
| Object | Círdan |
E821713
|
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: Círdan | Statement: [Nenning, associatedWithLord, Círdan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithLord Context triple: [Nenning, associatedWithLord, Círdan]
-
A.
associatedWithMonarch
Indicates a relationship where an entity has a connection or affiliation with a monarch, such as through service, governance, lineage, or formal association.
-
B.
lordOf
Indicates that one entity holds lordship, authority, or dominion over another entity.
-
C.
associatedWithNobleOrder
Indicates that an entity has a formal or recognized connection to a noble order, such as membership, affiliation, or honorary association.
-
D.
associatedWithFeudalOffice
Indicates a relationship where an entity is linked to, holds, or is otherwise connected with a specific feudal office or position within a feudal system.
-
E.
associatedWithPalace
Indicates a relationship where an entity has a connection, link, or involvement with a palace, such as through location, function, ownership, or affiliation.
- F. None of above. chosen
Provenance (5 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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a405118615081908b4beacfc191b4f6 |
completed | June 27, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:15 p.m.