Triple
T36711492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ἡρῳδιανοί |
E906804
|
entity |
| Predicate | stanceOnRome |
P98055
|
FINISHED |
| Object | υποστήριξη της ρωμαϊκής κυριαρχίας μέσω τῶν Ἡρωδιδῶν |
—
|
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: υποστήριξη της ρωμαϊκής κυριαρχίας μέσω τῶν Ἡρωδιδῶν | Statement: [Ἡρῳδιανοί, stanceOnRome, υποστήριξη της ρωμαϊκής κυριαρχίας μέσω τῶν Ἡρωδιδῶν]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stanceOnRome Context triple: [Ἡρῳδιανοί, stanceOnRome, υποστήριξη της ρωμαϊκής κυριαρχίας μέσω τῶν Ἡρωδιδῶν]
-
A.
stanceTowardRome
chosen
Indicates the nature or attitude of an entity’s position or policy in relation to Rome.
-
B.
roleInRome
Indicates that an entity holds or held a specific role, position, or function within the context of Rome or Roman society.
-
C.
allyOfRome
Indicates a relationship where one entity is politically or militarily aligned with, and offers support or cooperation to, Rome.
-
D.
aimOfRome
Indicates that something is the goal, purpose, or intended objective of Rome.
-
E.
significanceToRome
Indicates that something holds particular importance, influence, or relevance in relation to Rome.
- 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c813c44481908d6a261afcf6f857 |
completed | May 3, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.