Triple
T3160168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Machaerus |
E66082
|
entity |
| Predicate | constructionCenturyBC |
P6333
|
FINISHED |
| Object | 1st century BC |
—
|
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 BC | Statement: [Machaerus, constructionCenturyBC, 1st century BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionCenturyBC Context triple: [Machaerus, constructionCenturyBC, 1st century BC]
-
A.
constructionCentury
chosen
Indicates the century during which something was constructed or built.
-
B.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
C.
approximateBirthCenturyBCE
Indicates that an entity’s birth is estimated to have occurred within a specified century before the Common Era (BCE), rather than on an exact year or date.
-
D.
archaeologicallyExploredSince
Indicates that a place or site has been subject to archaeological exploration starting from a specified point in time.
-
E.
eraOfMajorConstruction
Indicates the time period during which the primary or most significant phase of construction for an entity took place.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada61606bc8190a8ad760d680924eb |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfe0a948190928f2201d671c654 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.