Triple
T4558776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lictors |
E120543
|
entity |
| Predicate | symbolCarried |
P40070
|
FINISHED |
| Object | fasces |
—
|
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: fasces | Statement: [Lictors, symbolCarried, fasces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolCarried Context triple: [Lictors, symbolCarried, fasces]
-
A.
symbolOnInsignia
Indicates that a particular symbol appears on or is featured as part of an insignia.
-
B.
carriedBy
Indicates that one entity is physically supported and transported by another entity.
-
C.
symbolDesigned
Indicates that one entity created or planned the design of a symbolic representation (such as a logo, icon, or emblem) for another entity.
-
D.
alsoCarries
chosen
Indicates that an entity, in addition to other items or responsibilities it has, carries another specified item or load as well.
-
E.
protectiveEmblemName
Indicates that a given name is the designated title or label of a protective emblem associated with an entity or context.
- 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.