Triple
T879059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Forbes |
E18985
|
entity |
| Predicate | feudalOrigin |
P1823
|
FINISHED |
| Object | medieval Scotland |
—
|
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: medieval Scotland | Statement: [Lord Forbes, feudalOrigin, medieval Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feudalOrigin Context triple: [Lord Forbes, feudalOrigin, medieval Scotland]
-
A.
associatedWithFeudalSystem
Indicates a relationship in which something is connected, linked, or relevant to the structures, practices, or institutions of a feudal system.
-
B.
feudalStatus
Indicates the hierarchical social or legal position an entity holds within a feudal system, such as lord, vassal, or serf.
-
C.
isFeudal
Indicates that one entity holds a feudal relationship to another, typically involving hierarchical obligations such as land tenure, service, or allegiance.
-
D.
medievalState
Indicates that an entity functioned as a state or political unit during the medieval historical period.
-
E.
historicalOrigin
chosen
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4acb1dc20819095b9bb093158b60d |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8d47c081909b02a53e305ccf7a |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.