Triple
T28119112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silanus |
E710725
|
entity |
| Predicate | usedByNobles |
P64068
|
FINISHED |
| Object | late Republic |
—
|
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: late Republic | Statement: [Silanus, usedByNobles, late Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByNobles Context triple: [Silanus, usedByNobles, late Republic]
-
A.
usedByNobility
chosen
Indicates that something is employed, possessed, or utilized specifically by members of the nobility.
-
B.
usedByNobleFamily
Indicates that something is employed, possessed, or otherwise utilized by a noble family.
-
C.
usedAsRoyalFavor
Indicates that something is employed or granted as a token of royal favor, privilege, or goodwill from a monarch or ruling authority.
-
D.
notableNoble
Indicates that an entity is a noble who is particularly prominent, distinguished, or widely recognized in some notable way.
-
E.
noblePrivilege
Indicates that an entity possesses special rights, immunities, or advantages granted by virtue of noble or aristocratic status.
- 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_69ef9b72f63081909dfbc2c1ddae86c6 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:16 p.m.