Triple
T20012520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bassanio |
E494622
|
entity |
| Predicate | isInRelationshipType |
P56596
|
FINISHED |
| Object | husband of Portia |
—
|
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: husband of Portia | Statement: [Bassanio, isInRelationshipType, husband of Portia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInRelationshipType Context triple: [Bassanio, isInRelationshipType, husband of Portia]
-
A.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
-
B.
hasMaritalRelationshipType
chosen
Indicates the specific type or nature of the marital relationship that exists between two entities.
-
C.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
D.
basisOfRelationship
Indicates that one entity serves as the foundational reason, cause, or justification for the relationship that exists between two or more entities.
-
E.
roleInRelationship
Indicates that an entity holds a specific role or position within a defined relationship between two or more entities.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66238f434819083b11458179bb601 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:34 p.m.