Triple
T31503979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leiningen-Dagsburg |
E803764
|
entity |
| Predicate | hasPrimaryPowerBase |
P112282
|
FINISHED |
| Object | southwestern Germany |
—
|
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: southwestern Germany | Statement: [Leiningen-Dagsburg, hasPrimaryPowerBase, southwestern Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryPowerBase Context triple: [Leiningen-Dagsburg, hasPrimaryPowerBase, southwestern Germany]
-
A.
hasPowerBase
chosen
Indicates that an entity derives support, influence, or authority from a particular group, location, or resource that serves as its primary base of power.
-
B.
hasCorePower
Indicates that an entity possesses a primary or fundamental power, ability, or capability that defines its essential function or role.
-
C.
hasPowerHouse
Indicates that one entity possesses or contains a primary energy-producing or central operational unit (a "power house") associated with it.
-
D.
hasPowerTerminal
Indicates that an entity is equipped with or connected to a power terminal through which electrical power can be supplied or distributed.
-
E.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a006fe981488190b4287289a3327664 |
completed | May 10, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_6a006f6976ec8190ba2c04fbaa946345 |
completed | May 10, 2026, 11:43 a.m. |
Created at: April 30, 2026, 9:46 p.m.