Triple
T31995449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rothbart |
E816980
|
entity |
| Predicate | roleInRelationTo |
P77541
|
FINISHED |
| Object | the White Swan |
—
|
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: the White Swan | Statement: [Rothbart, roleInRelationTo, the White Swan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInRelationTo Context triple: [Rothbart, roleInRelationTo, the White Swan]
-
A.
roleInRelationship
chosen
Indicates that an entity holds a specific role or position within a defined relationship between two or more entities.
-
B.
occursInRelationTo
Indicates that an event, process, or state takes place in the context of, or with reference to, another specified entity or relationship.
-
C.
termRelationTo
Indicates a general relational association between one term and another, without specifying the exact nature of that relationship.
-
D.
standsInRelationTo
Indicates that one entity is connected to another by some specified relationship, without constraining the nature or direction of that relationship.
-
E.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
- 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_69fff86e544c81908063f61b876c9d78 |
completed | May 10, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fff7e7cb688190977eeca41aad25b9 |
completed | May 10, 2026, 3:13 a.m. |
Created at: May 1, 2026, 12:13 a.m.