Triple
T31945674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H 81 |
E815644
|
entity |
| Predicate | referredWorkPeriod |
P137798
|
FINISHED |
| Object | Romantic era |
—
|
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: Romantic era | Statement: [H 81, referredWorkPeriod, Romantic era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referredWorkPeriod Context triple: [H 81, referredWorkPeriod, Romantic era]
-
A.
basedOnWorkPeriod
Indicates that something is determined, calculated, or defined according to a specific period of work or employment.
-
B.
timePeriodOfWorks
chosen
Indicates the span of time during which the associated works were created, produced, or active.
-
C.
occupationDuration
Indicates the length of time an entity holds or has held a particular occupation or role.
-
D.
collaborationPeriodWith
Indicates the time span during which two or more entities are engaged in a collaborative relationship or joint activity.
-
E.
collaborationPeriod
Indicates the time span during which two or more entities are actively engaged in a collaborative relationship or joint activity.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: May 1, 2026, 12:06 a.m.