Triple
T36166426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen of Technicolor |
E1046010
|
entity |
| Predicate | appliedToPersonSpouse |
P200111
|
FINISHED |
| Object | Hall Bartlett |
—
|
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: Hall Bartlett | Statement: [Queen of Technicolor, appliedToPersonSpouse, Hall Bartlett]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToPersonSpouse Context triple: [Queen of Technicolor, appliedToPersonSpouse, Hall Bartlett]
-
A.
spouseInstanceOf
Indicates that one entity is the specific spouse (marriage partner) instance of another entity.
-
B.
spouseMemberOf
Indicates that a person’s spouse is a member of a specified group, organization, or entity.
-
C.
associatedWithFieldThroughSpouse
Indicates that an entity is connected to a particular field or domain by virtue of their spouse’s involvement or association with that field.
-
D.
spouseIn
Indicates that one entity is the spouse (married partner) of another entity within a specified context or grouping.
-
E.
spouseParticipantIn
Indicates that a person’s spouse is involved as a participant in a specified event, activity, or relationship.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff7595c9bc8190982c6e6e07a0c78f |
completed | May 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69ff715432a88190a25670d26614bde2 |
completed | May 9, 2026, 5:39 p.m. |
| PDg | Predicate description generation | batch_69ff7594c6c081909e812e4e04e63530 |
completed | May 9, 2026, 5:57 p.m. |
Created at: May 3, 2026, 4:08 p.m.