Triple
T3932092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marrucini |
E90816
|
entity |
| Predicate | eventualOutcome |
P24728
|
FINISHED |
| Object | assimilation 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: assimilation into Roman population | Statement: [Marrucini, eventualOutcome, assimilation into Roman population]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventualOutcome Context triple: [Marrucini, eventualOutcome, assimilation into Roman population]
-
A.
initialOutcome
Indicates the result or state that first occurs at the beginning of a process, event, or interaction, before any subsequent changes or outcomes.
-
B.
outcomeType
Indicates the specific category or nature of the result produced by an event, process, or action.
-
C.
outcomeOfTrial
Indicates that a particular result or verdict is produced as the consequence of a specific trial or legal proceeding.
-
D.
eventualFate
chosen
Indicates the ultimate outcome or final state that an entity is destined to reach over time.
-
E.
describesOutcomeOf
Indicates that one entity specifies or characterizes the result, consequence, or outcome produced by another entity or process.
- 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_69aed95f26e0819094b0e71974543a19 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeedaaf3c881909539831bf3a8bf10 |
completed | March 9, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69aee7625ad4819097e4e8a168c19274 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:23 p.m.