Triple
T17699478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principality of Galilee |
E441256
|
entity |
| Predicate | feudalRankOfRuler |
P106301
|
FINISHED |
| Object | prince |
—
|
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: prince | Statement: [Principality of Galilee, feudalRankOfRuler, prince]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feudalRankOfRuler Context triple: [Principality of Galilee, feudalRankOfRuler, prince]
-
A.
feudalStatus
Indicates the hierarchical social or legal position an entity holds within a feudal system, such as lord, vassal, or serf.
-
B.
monarchicRank
Indicates the hierarchical level or status an individual holds within a monarchical system of rule.
-
C.
rulerOf
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
-
D.
isFeudalTitle
chosen
Indicates that the subject is a title associated with a feudal hierarchy, such as those held within a system of lords, vassals, and land-based obligations.
-
E.
roleInMonarchyPeriod
Indicates that an entity held a specific role or position during a defined period of a monarchy.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e471597d5c8190bd06337239739cd7 |
completed | April 19, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:04 a.m.