Triple
T32011081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harvey Cheyne Jr. |
E817402
|
entity |
| Predicate | formsDeepBondWith |
P68132
|
FINISHED |
| Object | Manuel Fidello |
—
|
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: Manuel Fidello | Statement: [Harvey Cheyne Jr., formsDeepBondWith, Manuel Fidello]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsDeepBondWith Context triple: [Harvey Cheyne Jr., formsDeepBondWith, Manuel Fidello]
-
A.
bondedWith
chosen
Indicates that two entities are joined by a strong, enduring connection or attachment, whether emotional, social, or structural.
-
B.
relationshipToBond
Indicates the specific type of personal, familial, or professional relationship an entity has to the person named Bond.
-
C.
pairBond
Indicates a long-term, typically exclusive social or reproductive partnership formed between two individuals.
-
D.
typicalBonding
Indicates a usual or characteristic bonding relationship that commonly occurs between the involved entities.
-
E.
formedDuoWith
Indicates that two entities joined together to create a duo, typically collaborating or acting as a pair for a shared purpose or activity.
- 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 1, 2026, 12:15 a.m.