Triple
T26811424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asopus (Boeotia) |
E672006
|
entity |
| Predicate | eraOfPrimaryAttestation |
P163463
|
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: [Asopus (Boeotia), eraOfPrimaryAttestation, antiquity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfPrimaryAttestation Context triple: [Asopus (Boeotia), eraOfPrimaryAttestation, antiquity]
-
A.
primaryAttestation
Indicates that something serves as the main or original source of evidence or documentation for a given entity or claim.
-
B.
timeOfAttestation
Indicates the specific time at which a statement, document, or claim is formally attested or verified.
-
C.
attestation
Indicates a formal declaration or confirmation that something is true, accurate, or has been verified.
-
D.
degreeOfAttestation
Indicates the extent or level to which something (such as a claim, form, or document) is supported, verified, or confirmed by evidence or authoritative sources.
-
E.
primaryEraEvaluated
Indicates that an entity has been assessed or analyzed with respect to its main or most relevant historical era or time period.
- 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f638344b148190bf0414ef7c5f1f38 |
completed | May 2, 2026, 5:45 p.m. |
Created at: April 27, 2026, 4:29 a.m.