Triple
T29735478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pompeii Rufi |
E752445
|
entity |
| Predicate | relatedGens |
P124948
|
FINISHED |
| Object | gens Pompeia |
E212515
|
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: gens Pompeia | Statement: [Pompeii Rufi, relatedGens, gens Pompeia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedGens Context triple: [Pompeii Rufi, relatedGens, gens Pompeia]
-
A.
associatedGens
Indicates a relationship where one entity is linked or connected to one or more genes in some relevant biological or functional context.
-
B.
geneticRelation
Indicates that two entities are connected through a hereditary or familial genetic relationship.
-
C.
relatedPass
Indicates that one pass is associated with or connected to another pass in some relevant way.
-
D.
secondGenerationRelatedTo
Indicates a relationship where one entity is in the second generation relative to another, such as a grandchild, grandparent, or equivalent two-generation familial link.
-
E.
lineageRelatedTo
chosen
Indicates a relationship where two entities are connected through a line of descent or ancestry within the same lineage.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a01a819644c819094c58d083d525da0 |
completed | May 11, 2026, 9:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a26c8e6fa5c81908c63cc4350978226 |
completed | June 8, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_6a01a5dfd628819083c032d8cfd2e726 |
completed | May 11, 2026, 9:48 a.m. |
Created at: April 28, 2026, 7:45 p.m.