Triple
T28410457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noviodunum |
E719647
|
entity |
| Predicate | navalFleetStationed |
P165747
|
FINISHED |
| Object | Classis Flavia Moesica |
—
|
NE NERFINISHED |
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: Classis Flavia Moesica | Statement: [Noviodunum, navalFleetStationed, Classis Flavia Moesica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalFleetStationed Context triple: [Noviodunum, navalFleetStationed, Classis Flavia Moesica]
-
A.
navalBaseLocation
Indicates the geographic location where a naval base is situated or established.
-
B.
navalFacilityName
Indicates that a naval facility is associated with a specific proper name or designation.
-
C.
navalFleet
Indicates a relationship where multiple naval vessels are organized and operate together as a coordinated maritime military force.
-
D.
countryNavalForce
Indicates that a country possesses, controls, or is associated with a particular naval military force.
-
E.
hasNavalFacility
Indicates that one entity possesses, hosts, or contains a naval facility (such as a naval base, port, or installation) associated with it.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a6babcc81908052c9907a99c882 |
completed | May 2, 2026, 8:11 p.m. |
Created at: April 28, 2026, 1:26 a.m.