Triple
T31335094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keith Anderson |
E799149
|
entity |
| Predicate | spouseWeddingLocation |
P27490
|
FINISHED |
| Object | Chicago |
—
|
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: Chicago | Statement: [Keith Anderson, spouseWeddingLocation, Chicago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseWeddingLocation Context triple: [Keith Anderson, spouseWeddingLocation, Chicago]
-
A.
marriageLocation
chosen
Indicates the place where a marriage ceremony or legal union between two people took place.
-
B.
spouseTravelDestination
Indicates that a location is the place where a person’s spouse is traveling or intends to travel.
-
C.
betrothalOrMarriagePlace
Indicates the location where a betrothal or marriage event takes place.
-
D.
spouseAtEvent
Indicates that two individuals are spouses who are present together at a specific event.
-
E.
associatedWithWeddingOf
Indicates a relationship where something is connected or related to the wedding event of specific individuals.
- 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: April 29, 2026, 9:16 p.m.