Triple
T17095205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snyder family |
E414828
|
entity |
| Predicate | relationshipWeb |
P121666
|
FINISHED |
| Object | connected to Hughes family |
—
|
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: connected to Hughes family | Statement: [Snyder family, relationshipWeb, connected to Hughes family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWeb Context triple: [Snyder family, relationshipWeb, connected to Hughes family]
-
A.
relationshipNetwork
chosen
Indicates a connection between entities that are linked through a web of relationships, often capturing how they are associated or interact within a broader network.
-
B.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
-
C.
addressesRelationship
Indicates that one entity directs communication, remarks, or attention specifically toward another entity.
-
D.
playerRelations
Indicates the nature or status of the relationship between players, such as alliances, rivalries, or other interpersonal dynamics.
-
E.
relationshipFocus
Indicates a relationship where particular attention, priority, or emphasis is placed on the connection 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbfc9158819081689d3d594a1908 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.