Triple
T4558812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lictors |
E120543
|
entity |
| Predicate | loweredFascesBefore |
P57663
|
FINISHED |
| Object | the Roman people in assemblies |
—
|
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: the Roman people in assemblies | Statement: [Lictors, loweredFascesBefore, the Roman people in assemblies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loweredFascesBefore Context triple: [Lictors, loweredFascesBefore, the Roman people in assemblies]
-
A.
hasLowercaseForm
Indicates that one entity is the lowercase version or representation of another entity.
-
B.
hasLower
Indicates that one entity is positioned at a lower level, rank, or value relative to another entity.
-
C.
lowerRank
Indicates that one entity holds an inferior or subordinate rank, status, or position relative to another entity.
-
D.
lowerValueIndicates
Indicates that a smaller numerical value of a property or measurement corresponds to a greater degree, better outcome, or stronger presence of the relevant characteristic.
-
E.
shiftedUnder
Indicates that one entity has been moved or displaced to a position beneath another entity.
- 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd5829cc34819086ad2ae58446502e |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56f6e75481909c487a94a2c2d0ba |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:09 p.m.