Triple
T32967410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Marriage |
E843408
|
entity |
| Predicate | playwrightActivePeriod |
P98925
|
FINISHED |
| Object | early 3rd century BCE |
—
|
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: early 3rd century BCE | Statement: [The Marriage, playwrightActivePeriod, early 3rd century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playwrightActivePeriod Context triple: [The Marriage, playwrightActivePeriod, early 3rd century BCE]
-
A.
activeAsPlaywrightFrom
chosen
Indicates the time period during which an entity was actively working in the role of a playwright.
-
B.
laterPlaywright
Indicates that one person became a playwright at a later time than another person.
-
C.
hasPlaywrightDebutFor
Indicates that an entity made their first appearance or debut as a playwright specifically for a given work, production, or context.
-
D.
hasPlaywright
Indicates that one entity is the playwright who wrote or created the play associated with another entity.
-
E.
appearsInTimePeriod
Indicates that an entity is present, active, or occurs within a specified time period.
- 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.