Triple
T351124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elsa Einstein |
E7444
|
entity |
| Predicate | relationshipToAlbertEinstein |
P367
|
FINISHED |
| Object | second wife |
—
|
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: second wife | Statement: [Elsa Einstein, relationshipToAlbertEinstein, second wife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToAlbertEinstein Context triple: [Elsa Einstein, relationshipToAlbertEinstein, second wife]
-
A.
einsteinSignedOn
Indicates that Einstein formally agreed to, endorsed, or placed his signature on a specified document, proposal, or agreement.
-
B.
historicalRelationship
Indicates a relationship that existed between entities in the past, often tied to a specific historical period, context, or event.
-
C.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
D.
EinsteinDescription
Indicates that one entity provides a descriptive summary or characterization of Einstein.
-
E.
notableRelative
chosen
Indicates that an entity has a relative who is notable or well-known, specifying that familial relationship.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb7df63c8190b7cd1bcfdfd96187 |
completed | Feb. 28, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69a2e955d1f88190bd687c46fa7c5469 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.