Triple
T7259570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anna Lie |
E159613
|
entity |
| Predicate | fieldConnectedToThroughSpouse |
P55242
|
FINISHED |
| Object | mathematics |
—
|
LITERAL FINISHED |
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: mathematics | Statement: [Anna Lie, fieldConnectedToThroughSpouse, mathematics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldConnectedToThroughSpouse Context triple: [Anna Lie, fieldConnectedToThroughSpouse, mathematics]
-
A.
associatedWithFieldThroughSpouse
chosen
Indicates that an entity is connected to a particular field or domain by virtue of their spouse’s involvement or association with that field.
-
B.
metSpouseThrough
Indicates that one person became acquainted with and subsequently married their spouse as a result of a particular intermediary person, event, place, or context.
-
C.
governedThroughSpouse
Indicates that one entity exercised governing authority or political power indirectly through their spouse, who held the formal ruling position.
-
D.
spouseFamily
Indicates a family relationship formed through marriage, such as between a person and their spouse’s relatives.
-
E.
spouseInstanceOf
Indicates that one entity is the specific spouse (marriage partner) instance of another 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_69c68838f9948190875fd60b2351230c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb088dac8190b353f6ea3d686025 |
completed | March 27, 2026, 8:39 p.m. |
| PD | Predicate disambiguation | batch_69c6e76876608190ac4652bc7153302e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:57 p.m.