Triple
T37369394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voronwë |
E927795
|
entity |
| Predicate | associatedVala |
P205865
|
FINISHED |
| Object | Ulmo |
E823161
|
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: Ulmo | Statement: [Voronwë, associatedVala, Ulmo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedVala Context triple: [Voronwë, associatedVala, Ulmo]
-
A.
servedVala
Indicates that one entity performed service, assistance, or duties for another entity named Vala.
-
B.
associatedValue
Indicates that one entity is linked to another entity that serves as its corresponding or contextually related value.
-
C.
usesVAR
Indicates that one entity makes use of, employs, or utilizes another entity as a variable or resource in performing some function or operation.
-
D.
associatedVow
Indicates a relationship where a vow is linked or connected to a particular entity or event.
-
E.
patronVala
Indicates a relationship where one entity acts as a patron, sponsor, or benefactor providing support or backing to another entity.
- 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a408240b2448190aeb16ed703341838 |
completed | June 28, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
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:16 p.m.