Triple
T6599784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Wessex |
E148566
|
entity |
| Predicate | hasCoreFunction |
P71974
|
FINISHED |
| Object | rule the Kingdom of Wessex |
—
|
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: rule the Kingdom of Wessex | Statement: [King of Wessex, hasCoreFunction, rule the Kingdom of Wessex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreFunction Context triple: [King of Wessex, hasCoreFunction, rule the Kingdom of Wessex]
-
A.
hasCore
Indicates that one entity possesses, contains, or is built around a central or most essential component represented by another entity.
-
B.
hasCoreClass
Indicates that an entity is associated with, or belongs to, a primary or fundamental class within a classification system.
-
C.
hasCoreUnit
Indicates that an entity includes or is composed around a primary, central, or fundamental unit.
-
D.
hasCoreService
Indicates that an entity provides, includes, or is associated with a primary or fundamental service that forms the central part of its offering or functionality.
-
E.
hasCoreValue
Indicates that an entity possesses or is characterized by a fundamental guiding principle or core belief.
- 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_69c687e7b8688190811ffee72e096468 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acfd17388190bd0bb8b2371e7df1 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6cc988c0081909d22b86ca299331c |
completed | March 27, 2026, 6:29 p.m. |
Created at: March 27, 2026, 1:56 p.m.