Triple
T2030391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabines |
E44501
|
entity |
| Predicate | eventualStatus |
P13710
|
FINISHED |
| Object | assimilated into Roman population |
—
|
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: assimilated into Roman population | Statement: [Sabines, eventualStatus, assimilated into Roman population]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventualStatus Context triple: [Sabines, eventualStatus, assimilated into Roman population]
-
A.
laterStatus
chosen
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
B.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
C.
earlierStatus
Indicates that one status or condition occurred or was valid before another status in time.
-
D.
eventualSuccessor
Indicates that one entity will become the successor of another at some later point in time, rather than immediately.
-
E.
seeksStatusAs
Indicates that one entity is attempting to obtain or be recognized with a particular status, role, or standing in relation to another entity.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb915c9548190809d08c4d67466fb |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a656248190ac2ced196b35bc6b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.