Triple
T36515437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mamercus |
E900023
|
entity |
| Predicate | typicalBearersStatus |
P34346
|
FINISHED |
| Object | patrician magistrates |
—
|
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: patrician magistrates | Statement: [Mamercus, typicalBearersStatus, patrician magistrates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBearersStatus Context triple: [Mamercus, typicalBearersStatus, patrician magistrates]
-
A.
typicalBearers
chosen
Indicates that certain entities are the usual or characteristic holders, users, or possessors of a given property, role, or attribute.
-
B.
bearerStatus
Indicates that one entity holds or possesses another entity in a specific role, capacity, or state (i.e., is the bearer of it).
-
C.
typicalBearersNationality
Indicates the nationality that entities of a given type or class are most commonly associated with.
-
D.
hasMultipleBearers
Indicates that a single item, attribute, or role is associated with more than one bearer or holder simultaneously.
-
E.
typicalNameBearers
Indicates that the subject is a common or characteristic name borne by the entities in the object set.
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.