Triple
T31995396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swan Queen |
E816979
|
entity |
| Predicate | pairedWithRole |
P74541
|
FINISHED |
| Object | Prince Siegfried |
—
|
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: Prince Siegfried | Statement: [Swan Queen, pairedWithRole, Prince Siegfried]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pairedWithRole Context triple: [Swan Queen, pairedWithRole, Prince Siegfried]
-
A.
pairedWithRelationshipName
Indicates that one entity is associated with another as a named pair within a specific relationship context.
-
B.
pairedWithFunctionally
Indicates that one entity is functionally matched or coupled with another to perform a complementary or corresponding role.
-
C.
pairedWithName
Indicates that one entity is associated or matched with another entity identified by a specific name.
-
D.
pairedSingleWith
chosen
Indicates that one entity is matched or associated as a single counterpart with another single entity, typically forming an exclusive one-to-one pairing.
-
E.
pairBond
Indicates a long-term, typically exclusive social or reproductive partnership formed between two individuals.
- F. None of above.
Provenance (3 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b3f782788190aa4b2dfa9e6eab19 |
completed | May 3, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:13 a.m.