Triple
T3265931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Habsburg Spain |
E68526
|
entity |
| Predicate | dominantPowerIn |
P34275
|
FINISHED |
| Object | 16th century Europe |
—
|
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: 16th century Europe | Statement: [Habsburg Spain, dominantPowerIn, 16th century Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantPowerIn Context triple: [Habsburg Spain, dominantPowerIn, 16th century Europe]
-
A.
majorPowerIn
Indicates that an entity holds significant political, economic, or military influence within a specified domain, region, or context.
-
B.
dominantDuring
chosen
Indicates that one entity holds a prevailing or controlling influence over another specifically within a given time period or interval.
-
C.
dominantParty
Indicates that one party in a relationship holds primary control, authority, or influence over the other.
-
D.
dominantOn
Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
-
E.
majorPowerUntil
Indicates that an entity functioned as a major power or dominant force up to, but not beyond, a specified time or event.
- 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_69ad8590444081909e8107a8aeef3a23 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adafcc99908190897230b4b71e2ea8 |
completed | March 8, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69ada41d7eac8190ada4bf5f793d5c49 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.