Triple
T33573433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orphalese |
E859962
|
entity |
| Predicate | hasTemporalContextInWork |
P116502
|
FINISHED |
| Object | unspecified pre-modern era |
—
|
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: unspecified pre-modern era | Statement: [Orphalese, hasTemporalContextInWork, unspecified pre-modern era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTemporalContextInWork Context triple: [Orphalese, hasTemporalContextInWork, unspecified pre-modern era]
-
A.
hasTemporalOrderInWork
Indicates that one element in a work occurs before or after another element in the temporal sequence of that work.
-
B.
hasTemporalRole
Indicates that an entity participates in a role or function that is defined, constrained, or characterized by a specific time or temporal context.
-
C.
isContainedInWorkBy
Indicates that something is included within, or forms a part of, a larger work created by a specified agent.
-
D.
hasTemporalUse
Indicates that something is used, applicable, or valid only during a specific time or temporal interval.
-
E.
containsWorkFromPeriod
chosen
Indicates that something includes or features work that originates from a specified historical or temporal 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: May 1, 2026, 1:40 a.m.