Triple
T24912438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giacomo Sumner |
E623881
|
entity |
| Predicate | parentalMarriage |
P81808
|
FINISHED |
| Object | Sting and Trudie Styler |
—
|
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: Sting and Trudie Styler | Statement: [Giacomo Sumner, parentalMarriage, Sting and Trudie Styler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentalMarriage Context triple: [Giacomo Sumner, parentalMarriage, Sting and Trudie Styler]
-
A.
parentsMarriageStatus
chosen
Indicates the marital status relationship between an individual’s parents (e.g., married, divorced, separated, never married).
-
B.
parentsMarriedAt
Indicates that the parents of the given entity were married at the specified time or date.
-
C.
marital status
Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
-
D.
marriageOutcome
Indicates the result or status that follows from a marriage, such as whether it continues, ends, or changes form.
-
E.
maritalRelations
Indicates a legally or socially recognized spousal relationship or marriage-based connection between two entities.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:28 a.m.