Triple
T30162169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lex Manilia |
E766696
|
entity |
| Predicate | grantedCommandOver |
P7884
|
FINISHED |
| Object | Roman forces in the East |
—
|
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: Roman forces in the East | Statement: [Lex Manilia, grantedCommandOver, Roman forces in the East]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedCommandOver Context triple: [Lex Manilia, grantedCommandOver, Roman forces in the East]
-
A.
commandedBy
Indicates that one entity holds authoritative control or issues orders over another entity.
-
B.
commandedTo
Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
-
C.
grantedBy
Indicates that a right, permission, or benefit is conferred or authorized by one entity to another.
-
D.
grantedPower
chosen
Indicates that one entity has conferred authority, control, or a specific capability to another entity.
-
E.
coCommandedWith
Indicates that two or more entities shared command authority together over the same unit, operation, or context during a given period.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 29, 2026, 7:22 p.m.