Triple
T37359032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Countess Almaviva |
E927529
|
entity |
| Predicate | marriedNameDerivedFrom |
P14292
|
FINISHED |
| Object | Count Almaviva |
—
|
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: Count Almaviva | Statement: [Countess Almaviva, marriedNameDerivedFrom, Count Almaviva]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriedNameDerivedFrom Context triple: [Countess Almaviva, marriedNameDerivedFrom, Count Almaviva]
-
A.
laterMarriedName
Indicates that the referenced name is a surname or full name a person adopted after a later marriage, replacing or succeeding their previous name.
-
B.
hasMarriedSurname
chosen
Indicates that a person’s current surname is the one they adopted through marriage.
-
C.
maidenNameOf
Indicates that one person’s original family surname before marriage is the maiden name of another person.
-
D.
spouseNameAtMarriage
Indicates the full name a person’s spouse had at the time of their marriage.
-
E.
eraNameOfSpouse
Indicates that the value is the name of the historical era associated with the spouse of the subject.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: May 3, 2026, 4:16 p.m.