Triple
T23859577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Countess of Fife |
E592404
|
entity |
| Predicate | territorialPower |
P154216
|
FINISHED |
| Object | significant |
—
|
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: significant | Statement: [Countess of Fife, territorialPower, significant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: territorialPower Context triple: [Countess of Fife, territorialPower, significant]
-
A.
territorialAmbition
Indicates a desire or intent by one entity to expand its control, ownership, or influence over additional geographic areas or territories.
-
B.
mainTerritoryOfInfluence
Indicates the primary geographic area where an entity exerts the most significant control, impact, or influence.
-
C.
territorial
Indicates that one entity claims, defends, or is associated with control over a specific area or domain in relation to another entity.
-
D.
territorialLevel
Indicates the administrative or geographic tier at which something is defined, applied, or governed within a territorial hierarchy.
-
E.
hasTerritorialPossession
Indicates that one entity holds ownership, control, or legal rights over a specific territory or geographic area.
- F. None of above. chosen
Provenance (4 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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cadebc6481909110a2a5fe85c93f |
completed | April 29, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:12 p.m.