Triple
T17302210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juno Sospita |
E420064
|
entity |
| Predicate | cultIntegratedInto |
P106007
|
FINISHED |
| Object | state religion of Rome |
—
|
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: state religion of Rome | Statement: [Juno Sospita, cultIntegratedInto, state religion of Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultIntegratedInto Context triple: [Juno Sospita, cultIntegratedInto, state religion of Rome]
-
A.
previouslyIntegratedInto
Indicates that an entity was formerly incorporated or included as part of another entity or system in the past.
-
B.
reintegratedInto
Indicates that an entity has been brought back and incorporated again into a group, system, or context it was previously separated from.
-
C.
integratedFrom
Indicates that something has been formed or constructed by combining or incorporating elements originating from another source.
-
D.
seeksToIntegrate
Indicates an effort or intention by one entity to combine, unify, or harmonize itself or its components with another entity or system.
-
E.
elementsIncorporatedInto
chosen
Indicates that one or more elements are taken in and made part of another entity, structure, or system.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e438fba938819084333764b868bd83 |
completed | April 19, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:41 a.m.