Triple
T8098075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gens Atia |
E189035
|
entity |
| Predicate | relativeStatus |
P45754
|
FINISHED |
| Object | minor Roman gens |
—
|
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: minor Roman gens | Statement: [Gens Atia, relativeStatus, minor Roman gens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeStatus Context triple: [Gens Atia, relativeStatus, minor Roman gens]
-
A.
companionshipStatus
Indicates the current state or condition of a relationship of companionship between two or more entities.
-
B.
relationshipDynamic
Indicates a changing or evolving pattern of interaction between entities, such as shifts in their roles, closeness, or influence over time.
-
C.
associatedStatus
chosen
Indicates that one entity is linked to or characterized by a particular status or condition.
-
D.
proposedRelationship
Indicates that one entity has suggested or put forward the possibility of entering into a specific type of relationship with another entity.
-
E.
relationshipDurationWith
Indicates the length of time that a specified relationship between two entities has existed or is expected to last.
- 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_69ca82b886d88190a9cba0d5a4a27521 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4294b73481908c8373b8eca0f608 |
completed | March 31, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:30 p.m.