Triple
T32096311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen of the Woods |
E819730
|
entity |
| Predicate | associatedWithSpouse |
P33561
|
FINISHED |
| Object | Celeborn |
E271244
|
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: Celeborn | Statement: [Queen of the Woods, associatedWithSpouse, Celeborn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSpouse Context triple: [Queen of the Woods, associatedWithSpouse, Celeborn]
-
A.
associatedWithFieldThroughSpouse
Indicates that an entity is connected to a particular field or domain by virtue of their spouse’s involvement or association with that field.
-
B.
spouseAssociatedWith
chosen
Indicates a marital or spousal relationship or close association between two entities.
-
C.
spouseOfType
Indicates that one entity is the spouse of another, specifying the type or role of that spousal relationship.
-
D.
spouseIn
Indicates that one entity is the spouse (married partner) of another entity within a specified context or grouping.
-
E.
spouseInFamily
Indicates that a person is a spouse (married partner) within the context of a specific family unit.
- 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_6a34665a199481909267f54fa223b3be |
completed | June 18, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:26 a.m.