Triple
T20415782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gremio |
E500707
|
entity |
| Predicate | relationshipToHortensio |
P140055
|
FINISHED |
| Object | rival suitor |
—
|
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: rival suitor | Statement: [Gremio, relationshipToHortensio, rival suitor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToHortensio Context triple: [Gremio, relationshipToHortensio, rival suitor]
-
A.
relationshipToFlorentinoAriza
Indicates the nature of the relationship an entity has with Florentino Ariza.
-
B.
relationshipToDukeSenior
Indicates that one entity holds a specified familial or social relationship to an older or higher-ranking duke.
-
C.
relationshipToFalstaff
Indicates the specific interpersonal or social connection that one entity has to Falstaff.
-
D.
relationshipToTheMiller'sTale
Indicates a relationship in which something is connected or relevant to "The Miller's Tale," such as being about it, derived from it, or otherwise associated with it.
-
E.
relationshipToHermia
Indicates the specific type of personal or social relationship that one entity has with Hermia.
- F. None of above. chosen
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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67a437eec8190a20c89a236dd5bc0 |
completed | April 20, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d766b408190a1d3698145fb6d30 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:30 a.m.