Triple
T27554457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuor |
E695593
|
entity |
| Predicate | patronVala |
P163282
|
FINISHED |
| Object | Ulmo |
—
|
NE NERFINISHED |
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: [Tuor, patronVala, Ulmo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patronVala Context triple: [Tuor, patronVala, Ulmo]
-
A.
patronType
Indicates the classification or category of a patron in relation to a service, institution, or resource.
-
B.
coPatron
Indicates a relationship where two or more entities share joint responsibility or role as patrons supporting the same person, group, or endeavor.
-
C.
patronState
Indicates a relationship where one state acts as a protector, sponsor, or dominant supporter of another state or political entity.
-
D.
patroness
Indicates that a female person supports, sponsors, or acts as a benefactor for someone or something.
-
E.
patronFamily
Indicates that one family serves as a patron or protector, providing support or sponsorship to another family.
- F. None of above. chosen
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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6369a22688190a5674191c90a5d12 |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 1:36 p.m.