Triple
T36449952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galarina |
E897979
|
entity |
| Predicate | hasSpousalRelationshipContext |
P74827
|
FINISHED |
| Object | Gala Dalí |
—
|
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: Gala Dalí | Statement: [Galarina, hasSpousalRelationshipContext, Gala Dalí]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpousalRelationshipContext Context triple: [Galarina, hasSpousalRelationshipContext, Gala Dalí]
-
A.
spouseRelationshipContext
chosen
Indicates a marital relationship context between two entities, specifying that they are spouses or partners in a recognized marriage-like union.
-
B.
hasMaritalRelationshipType
Indicates the specific type or nature of the marital relationship that exists between two entities.
-
C.
spouseInstanceOf
Indicates that one entity is the specific spouse (marriage partner) instance of another entity.
-
D.
hasCollaborativeRoleWithSpouse
Indicates that an individual shares a joint, cooperative role or responsibility together with their spouse.
-
E.
hasMemberSpouseConnection
Indicates a relationship where one entity is a spouse of a member associated with the other entity.
- 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_69f76e5720b481908f8177ac24a7560b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: May 3, 2026, 4:10 p.m.