Triple
T6526520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ancient and Medieval Art Department |
E151315
|
entity |
| Predicate | associatedWithTimeSpan |
P302
|
FINISHED |
| Object | antiquity |
—
|
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: antiquity | Statement: [Ancient and Medieval Art Department, associatedWithTimeSpan, antiquity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithTimeSpan Context triple: [Ancient and Medieval Art Department, associatedWithTimeSpan, antiquity]
-
A.
associatedWithTime
Indicates a relationship where something is linked or connected to a specific point or period in time.
-
B.
associatedPeriodEnd
Indicates the ending point or final date of the time period with which something is associated.
-
C.
collectionTimespan
Indicates the time period over which a collection exists, is accumulated, or is considered valid.
-
D.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
-
E.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ada8a0e48190947616f3a09a2cba |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:45 p.m.