Triple
T20984013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salanio |
E516844
|
entity |
| Predicate | closelyAssociatedWithGroup |
P47706
|
FINISHED |
| Object | Antonio’s circle of friends |
—
|
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: Antonio’s circle of friends | Statement: [Salanio, closelyAssociatedWithGroup, Antonio’s circle of friends]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closelyAssociatedWithGroup Context triple: [Salanio, closelyAssociatedWithGroup, Antonio’s circle of friends]
-
A.
refersToGroupAssociatedWith
Indicates that one entity makes reference to a group that is associated or linked with another specified entity.
-
B.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
C.
associatedWithCharacterGroup
chosen
Indicates that an entity has a connection or affiliation with a particular group of characters.
-
D.
associatedWithCityGroup
Indicates a relationship where an entity is linked or connected to a specific group or collection of cities.
-
E.
memberOfGroupWith
Indicates that an entity belongs to, or is associated as a member with, a particular group or collection of 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fbe1474c8190912b90da0973f99f |
completed | April 21, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:48 p.m.