Triple
T32505647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siegfried Fischbacher |
E830784
|
entity |
| Predicate | longTermPartner |
P174520
|
FINISHED |
| Object | Roy Horn |
—
|
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: Roy Horn | Statement: [Siegfried Fischbacher, longTermPartner, Roy Horn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longTermPartner Context triple: [Siegfried Fischbacher, longTermPartner, Roy Horn]
-
A.
lifePartnerType
Indicates the type or category of a person’s life partner in a long-term or committed relationship.
-
B.
intendedPartner
Indicates that one entity is designated or expected to be the future or planned partner (e.g., romantic, marital, or business) of another entity.
-
C.
isShortLivedPartnerOf
Indicates a partnership relationship between two entities that is brief or temporary in duration.
-
D.
longtimeManufacturerPartner
Indicates a relationship where one entity has served as a manufacturer for another entity over a long, sustained period of time.
-
E.
symbolicPartnerOf
Indicates a relationship in which two entities are formally or representationally associated as partners in a symbolic, rather than practical or operational, sense.
- F. None of above. chosen
Provenance (4 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c44b26a88190be979e894c7dfd38 |
completed | May 3, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 1 a.m.