Triple
T18443637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Crown |
E450597
|
entity |
| Predicate | hasDiscoveryEpoch |
P26767
|
FINISHED |
| Object | 2nd 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: 2nd century | Statement: [Southern Crown, hasDiscoveryEpoch, 2nd century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiscoveryEpoch Context triple: [Southern Crown, hasDiscoveryEpoch, 2nd century]
-
A.
hasDiscoveryPeriod
chosen
Indicates the time span during which a particular discovery was made or recognized.
-
B.
hasDiscoveryStatus
Indicates the current state or phase of discovery or identification associated with an entity.
-
C.
hasDiscovered
Indicates that one entity has found, detected, or uncovered the existence, presence, or truth of another entity or phenomenon.
-
D.
discoveredSince
Indicates that one entity has been discovered starting from, or at some point after, a specified time or event associated with another entity.
-
E.
hasDiscoveryFeature
Indicates that an entity includes or supports a capability for discovering, finding, or surfacing other relevant entities, items, or information.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c12a0248190a848a1fe833a1975 |
completed | April 19, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:30 a.m.