Triple
T31592268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legio XVII |
E806129
|
entity |
| Predicate | legionNumberReused |
P120504
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Legio XVII, legionNumberReused, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legionNumberReused Context triple: [Legio XVII, legionNumberReused, false]
-
A.
legionNumber
chosen
Indicates the numerical designation assigned to a specific legion within a larger military or organizational structure.
-
B.
hullNumberReusedFrom
Indicates that a vessel’s hull number was previously assigned to another vessel and has been reused from that earlier assignment.
-
C.
reusedIn
Indicates that something previously used in one context or instance is used again in another context or instance.
-
D.
legionStationed
Indicates that a specific legion is stationed or deployed at a particular location.
-
E.
previouslyUsedNumberDesignationsUntil
Indicates that certain number designations were used for an entity up until a specified point in time, after which they were no longer in use.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8316e748190a5362888ba07ee07 |
completed | May 3, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:28 p.m.