Triple
T13771658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ancient Greek sculpture |
E330894
|
entity |
| Predicate | hasEndCentury |
P10339
|
FINISHED |
| Object | 1st 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: 1st century BCE | Statement: [Ancient Greek sculpture, hasEndCentury, 1st century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndCentury Context triple: [Ancient Greek sculpture, hasEndCentury, 1st century BCE]
-
A.
endedInCentury
chosen
Indicates that an event, period, or process concluded during a specified century.
-
B.
approximateUseEndCentury
Indicates that something’s period of use ended around, but not necessarily exactly in, a specified century.
-
C.
latestCentury
Indicates that the associated time or event occurs in, or belongs to, the most recent century relative to a given reference point.
-
D.
declaredInCentury
Indicates that something (such as an event, work, or concept) was formally declared or proclaimed during a specified century.
-
E.
acquiredInCentury
Indicates that one entity was acquired during a specific century represented by the other entity.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0235aea881909ab4c721db081b00 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:10 p.m.