Triple
T34795125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gertrude Morel |
E1003055
|
entity |
| Predicate | hasStrongBondWith |
P96771
|
FINISHED |
| Object | Paul Morel |
—
|
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: Paul Morel | Statement: [Gertrude Morel, hasStrongBondWith, Paul Morel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrongBondWith Context triple: [Gertrude Morel, hasStrongBondWith, Paul Morel]
-
A.
bondedWith
Indicates that two entities are joined by a strong, enduring connection or attachment, whether emotional, social, or structural.
-
B.
hasStrongTiesTo
chosen
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.
bondedWithSpecies
Indicates a relationship where an entity has formed a close, enduring bond or attachment with a particular species.
-
E.
formsBondOver
Indicates that two or more entities develop a connection or relationship specifically through a shared experience, interest, 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ffc083a54c8190ac80d05ee8d20a6b |
completed | May 9, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69ffbfeb05b88190b4d50ce8124004d9 |
completed | May 9, 2026, 11:14 p.m. |
Created at: May 3, 2026, 3:59 p.m.