Triple
T1042926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman fasces |
E22507
|
entity |
| Predicate | carriedInNumber |
P20642
|
FINISHED |
| Object | twelve fasces for Roman consuls |
—
|
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: twelve fasces for Roman consuls | Statement: [Roman fasces, carriedInNumber, twelve fasces for Roman consuls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriedInNumber Context triple: [Roman fasces, carriedInNumber, twelve fasces for Roman consuls]
-
A.
carriedBy
Indicates that one entity is physically supported and transported by another entity.
-
B.
carriedPrisonersFrom
Indicates that an entity transported prisoners away from a specified origin location or source.
-
C.
isNumbered
Indicates that an entity has been assigned a specific number or position in an ordered sequence.
-
D.
numberInInstrument
chosen
Indicates that an entity specifies the count or quantity of items contained within or associated with a particular instrument.
-
E.
cargoSpace
Indicates that one entity provides storage capacity or room for carrying goods, equipment, or other items for another entity.
- 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b845fa8c8190a7b69629883b62e2 |
completed | March 1, 2026, 10:05 p.m. |
| PD | Predicate disambiguation | batch_69a4b72ba60881908b017ef3b2b9645e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.