Triple
T35569489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camerinus |
E1027870
|
entity |
| Predicate | typicalBearersBelongTo |
P116510
|
FINISHED |
| Object | Sulpicia gens |
E2146022
|
NE 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: Sulpicia gens | Statement: [Camerinus, typicalBearersBelongTo, Sulpicia gens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBearersBelongTo Context triple: [Camerinus, typicalBearersBelongTo, Sulpicia gens]
-
A.
typicalBearers
Indicates that certain entities are the usual or characteristic holders, users, or possessors of a given property, role, or attribute.
-
B.
bearersBelongedTo
Indicates that the entities serving as bearers were members of, or affiliated with, a particular group, organization, or owner.
-
C.
typicalBearersNationality
Indicates the nationality that entities of a given type or class are most commonly associated with.
-
D.
associatedWithStateThroughBearers
Indicates a relationship where an entity is linked to a state indirectly via intermediary bearers (such as organizations, agents, or instruments) that connect it to that state.
-
E.
typicalNameBearers
chosen
Indicates that the subject is a common or characteristic name borne by the entities in the object set.
- F. None of above.
Provenance (4 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a385bd08fac81908a8971c3a1101890 |
completed | June 21, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.