Triple
T9548890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scott Thorson |
E230367
|
entity |
| Predicate | relationshipTypeWithLiberace |
P10690
|
FINISHED |
| Object | romantic partner |
—
|
LITERAL 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: romantic partner | Statement: [Scott Thorson, relationshipTypeWithLiberace, romantic partner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipTypeWithLiberace Context triple: [Scott Thorson, relationshipTypeWithLiberace, romantic partner]
-
A.
relationshipTypeWithLizzieEustace
Indicates the specific nature or category of relationship that an entity has with Lizzie Eustace.
-
B.
relationshipToCandide
Indicates the specific type of relationship or connection an entity has to the entity named Candide.
-
C.
relationshipTypeWith Alicia Johns
Indicates the specific type or nature of the relationship that an entity has with Alicia Johns.
-
D.
relationshipType
chosen
Indicates the specific kind of relationship that exists between two or more entities.
-
E.
performerRelationshipContext
Indicates the contextual nature or circumstances of the relationship between a performer and another entity (such as an event, work, or role).
- 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_69ca847c70b8819088a0a0bad64a50d6 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99059138819088ae54b26df979cf |
completed | April 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ccd58bd21881908b860e3ee469af13 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:02 p.m.