Triple
T32055548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legio II Italica |
E818607
|
entity |
| Predicate | dislocation |
P173159
|
FINISHED |
| Object | eastern Noricum |
—
|
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: eastern Noricum | Statement: [Legio II Italica, dislocation, eastern Noricum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dislocation Context triple: [Legio II Italica, dislocation, eastern Noricum]
-
A.
displacement
Indicates a change in an entity’s position from one location to another, typically specifying both direction and magnitude of that movement.
-
B.
fracture
Indicates a relationship where an object or material is broken or cracked into parts, typically due to applied stress or impact.
-
C.
displacementCause
Indicates a causal relationship where one entity is responsible for the displacement or forced movement of another entity from its original location or situation.
-
D.
dismembered
Indicates that one entity has cut or torn another entity’s body into separate parts, typically removing limbs or sections.
-
E.
tractionType
Indicates the type or method of traction applied or used in relation to an entity or system.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4efb0548190bb8f358c1623ca7d |
completed | May 3, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b267b90c8190807208cadce5ae8d |
completed | May 3, 2026, 2:26 a.m. |
Created at: May 1, 2026, 12:21 a.m.