Triple
T32967408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Marriage |
E843408
|
entity |
| Predicate | survivalOfText |
P139282
|
FINISHED |
| Object | no complete text extant |
—
|
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: no complete text extant | Statement: [The Marriage, survivalOfText, no complete text extant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivalOfText Context triple: [The Marriage, survivalOfText, no complete text extant]
-
A.
textualSurvival
chosen
Indicates that a text or written work has continued to exist, be transmitted, or remain accessible over time.
-
B.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
C.
survivesFor
Indicates that one entity continues to exist, endure, or remain functional for a specified duration or period.
-
D.
survivesIn
Indicates that an entity remains alive, functional, or intact within a specified environment, condition, or context.
-
E.
survivingUse
Indicates that one entity continues to make use of another entity or resource after an event that could have ended or invalidated that use.
- 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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d1a306b88190a14513a21ed4f076 |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:21 a.m.