Triple
T31639819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italicus |
E807414
|
entity |
| Predicate | countrySupportedBy |
P10546
|
FINISHED |
| Object | Roman Empire |
—
|
NE NERFINISHED |
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: Roman Empire | Statement: [Italicus, countrySupportedBy, Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countrySupportedBy Context triple: [Italicus, countrySupportedBy, Roman Empire]
-
A.
countryClaimSupported
Indicates that a claim made by a country is backed or endorsed by some form of support, such as evidence, recognition, or assistance.
-
B.
supportsCountry
chosen
Indicates that one entity provides assistance, endorsement, or backing to a specific country.
-
C.
countryImplements
Indicates that a country puts into effect, enforces, or carries out a specific policy, law, agreement, standard, or measure.
-
D.
countryResponse
Indicates that a country issues, provides, or expresses a reply, reaction, or stance in response to a particular event, request, or situation.
-
E.
countryStatus
Indicates the political or legal condition of a country, such as its sovereignty, recognition, or current state in international or domestic contexts.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fff59a00a881909b35b799654b3c45 |
completed | May 10, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69fff4d0a2e081909c972189b33d0128 |
completed | May 10, 2026, 3 a.m. |
Created at: April 30, 2026, 10:49 p.m.