Triple
T4558806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lictors |
E120543
|
entity |
| Predicate | stoodBeside |
P31095
|
FINISHED |
| Object | magistrates during official functions |
—
|
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: magistrates during official functions | Statement: [Lictors, stoodBeside, magistrates during official functions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stoodBeside Context triple: [Lictors, stoodBeside, magistrates during official functions]
-
A.
situatedOnSideOf
chosen
Indicates that one entity is located along or beside the lateral part or edge of another entity.
-
B.
positionedAgainst
Indicates that one entity is placed so that it directly faces or is set opposite to another entity, often in close or contacting alignment.
-
C.
locatedBehind
Indicates that one entity is positioned at the rear of or on the far side of another entity along a given viewing or reference direction.
-
D.
stoodAtStudAt
Indicates that one entity was positioned or located at a particular stud (e.g., structural post or support point).
-
E.
builtAlongside
Indicates that one entity was constructed next to or in parallel with another entity, typically during the same or a closely related time 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_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. |
Created at: March 20, 2026, 1:09 p.m.