Triple
T36921056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ninth Legion |
E913199
|
entity |
| Predicate | lastSecureAttestationDate |
P7428
|
FINISHED |
| Object | early 2nd century CE |
—
|
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: early 2nd century CE | Statement: [Ninth Legion, lastSecureAttestationDate, early 2nd century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastSecureAttestationDate Context triple: [Ninth Legion, lastSecureAttestationDate, early 2nd century CE]
-
A.
timeOfAttestation
chosen
Indicates the specific time at which a statement, document, or claim is formally attested or verified.
-
B.
certificationDate
Indicates the date on which an entity was officially certified or granted a formal certification.
-
C.
hasAttestation
Indicates that there exists a formal confirmation, evidence, or certification supporting the validity or authenticity of something.
-
D.
eraOfPrimaryAttestation
Indicates the historical time period during which the primary evidence or attestation of something first appears.
-
E.
attestation
Indicates a formal declaration or confirmation that something is true, accurate, or has been verified.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fdccda9881909409887cb8f533fb |
completed | May 5, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.