Triple
T22168614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Master drawings |
E547860
|
entity |
| Predicate | hasTemporalScopeEnd |
P118268
|
FINISHED |
| Object | 18th century |
—
|
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: 18th century | Statement: [Old Master drawings, hasTemporalScopeEnd, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTemporalScopeEnd Context triple: [Old Master drawings, hasTemporalScopeEnd, 18th century]
-
A.
hasTemporalEnd
chosen
Indicates that an event, state, or process concludes or terminates at a specific point or interval in time.
-
B.
temporal scope
Indicates the time period or duration over which a particular relationship, condition, or fact holds true.
-
C.
hasTemporalDefinition
Indicates that something is associated with a definition or specification that is constrained or characterized by time.
-
D.
hasTemporalAttribute
Indicates that an entity is associated with a specific temporal property or characteristic, such as time, duration, or period.
-
E.
hasTemporalUse
Indicates that something is used, applicable, or valid only during a specific time or temporal interval.
- 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_69e11e3c4c5c81908d336165816b12e0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a6721e8819081d732df2691f4a4 |
completed | April 28, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:34 p.m.