Triple
T17284343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casma |
E419611
|
entity |
| Predicate | hasNearbySitePeriod |
P126794
|
FINISHED |
| Object | Formative period |
—
|
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: Formative period | Statement: [Casma, hasNearbySitePeriod, Formative period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbySitePeriod Context triple: [Casma, hasNearbySitePeriod, Formative period]
-
A.
hasNearbySiteType
Indicates that one entity has another entity of a specified site type located in its close physical vicinity.
-
B.
hasNeighboringSite
Indicates that one site is located adjacent to or directly next to another site.
-
C.
hasNearbyHistoricPeriod
Indicates that one historic period occurs close in time or space to another historic period.
-
D.
hasNearbyMode
Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
-
E.
hasNearbySquare
Indicates that one entity has at least one square-shaped entity located close to it in space.
- F. None of above. chosen
Provenance (4 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e4332bd324819080795152293d6d43 |
completed | April 19, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:40 a.m.