Triple
T30317710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theodore II, Marquess of Montferrat |
E771100
|
entity |
| Predicate | realmCharacteristic |
P92453
|
FINISHED |
| Object | strategically important |
—
|
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: strategically important | Statement: [Theodore II, Marquess of Montferrat, realmCharacteristic, strategically important]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realmCharacteristic Context triple: [Theodore II, Marquess of Montferrat, realmCharacteristic, strategically important]
-
A.
domainCharacteristic
chosen
Indicates that a domain or area of interest possesses a particular characteristic or defining property.
-
B.
realmType
Indicates the classification or category of a realm, specifying what kind or type of realm it is.
-
C.
realmOftenIdentifiedWith
Indicates that one realm is frequently recognized, labeled, or regarded as being the same as, or equivalent to, another realm.
-
D.
realmName
Indicates the designated name or title assigned to a particular realm or domain.
-
E.
regionalCharacteristic
Indicates that a particular feature, quality, or attribute is typical of, or distinctive to, a specific geographic region.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 7:51 p.m.