Triple
T28624208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cannon family of Cambridge |
E724471
|
entity |
| Predicate | hasSocialTieTo |
P150269
|
FINISHED |
| Object | Harvard University |
—
|
NE NERFINISHED |
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: Harvard University | Statement: [Cannon family of Cambridge, hasSocialTieTo, Harvard University]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSocialTieTo Context triple: [Cannon family of Cambridge, hasSocialTieTo, Harvard University]
-
A.
hasSocialTieWith
chosen
Indicates a social relationship or connection exists between two entities, such as friendship, acquaintance, or other interpersonal tie.
-
B.
hasStrongTiesTo
Indicates a close, influential, and enduring relationship or connection exists between the referenced entities.
-
C.
haveRelationshipWith
Indicates that one entity is in some form of defined relationship or association with another entity.
-
D.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
E.
hasFriendship
Indicates a mutual, positive social relationship of friendship existing between two 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 28, 2026, 4:35 a.m.