Triple
T28474457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Classis Britannica |
E720523
|
entity |
| Predicate | likelyEstablished |
P158303
|
FINISHED |
| Object | 1st century AD |
—
|
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 AD | Statement: [Classis Britannica, likelyEstablished, 1st century AD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyEstablished Context triple: [Classis Britannica, likelyEstablished, 1st century AD]
-
A.
establishedFollowing
Indicates that one entity created or set up another entity after, and in consequence of, a prior entity or event.
-
B.
establishedAs
Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
-
C.
establishedTo
Indicates that one entity was created, founded, or set up for the purpose of serving, supporting, or enabling another entity.
-
D.
likelyStatus
chosen
Indicates the probable or expected state or condition of an entity based on available information or inference.
-
E.
claimedToHaveEstablished
Indicates that an entity asserts or alleges that it has created, founded, or set up another entity, organization, or structure.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 2:51 a.m.