Triple
T29704357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sempronius Gracchus |
E751583
|
entity |
| Predicate | hasFamilyBranchName |
P116433
|
FINISHED |
| Object | Gracchus |
—
|
NE NERFINISHED |
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: Gracchus | Statement: [Sempronius Gracchus, hasFamilyBranchName, Gracchus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyBranchName Context triple: [Sempronius Gracchus, hasFamilyBranchName, Gracchus]
-
A.
hasFamilyBranch
Indicates that one entity is a subdivision, offshoot, or branch within the broader family group or lineage of another entity.
-
B.
hasBranchName
chosen
Indicates that an entity (such as a branch or subdivision) bears or is identified by a specific branch name.
-
C.
hasFamilyNameOf
Indicates that one entity bears or uses the same family name (surname) as another entity.
-
D.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
-
E.
heldByFamilyBranch
Indicates that something is possessed, controlled, or maintained by a specific branch or sub-lineage of a family.
- 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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 28, 2026, 7:26 p.m.