Triple
T20012666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bargy |
E494626
|
entity |
| Predicate | hasNumberOfCompanionBaronies |
P138374
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Bargy, hasNumberOfCompanionBaronies, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfCompanionBaronies Context triple: [Bargy, hasNumberOfCompanionBaronies, 1]
-
A.
hasNotableBarony
Indicates that an entity possesses or is associated with a barony that is considered notable or significant in some context.
-
B.
hasFeudalOverlord
Indicates that one entity holds feudal lordship or overlord authority over another, implying hierarchical control and obligations within a feudal system.
-
C.
grantedFiefOf
Indicates that one party has been formally given control or ownership of a fief (landed estate) by another authority.
-
D.
vassalsOf
Indicates that one entity serves as a subordinate or dependent vassal under the authority or suzerainty of another entity.
-
E.
hasNotableMarquessate
Indicates that an entity holds or is associated with a marquessate that is considered historically or socially notable.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66238f434819083b11458179bb601 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:34 p.m.