Triple
T6414567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count |
E127790
|
entity |
| Predicate | associatedWithFeudalism |
P18765
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Count, associatedWithFeudalism, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFeudalism Context triple: [Count, associatedWithFeudalism, true]
-
A.
associatedWithFeudalSystem
chosen
Indicates a relationship in which something is connected, linked, or relevant to the structures, practices, or institutions of a feudal system.
-
B.
feudalType
Indicates the specific kind or category of feudal relationship, structure, or tenure that applies between the related entities.
-
C.
laterFeudalStatus
Indicates that one entity held a particular feudal status or rank at a later time than another entity or than an earlier status.
-
D.
isFeudal
Indicates that one entity holds a feudal relationship to another, typically involving hierarchical obligations such as land tenure, service, or allegiance.
-
E.
feudalStatus
Indicates the hierarchical social or legal position an entity holds within a feudal system, such as lord, vassal, or serf.
- 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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068e6bd3881909b1979de5cdf17fb |
completed | March 22, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69c060f5d4e481909d1366190607b586 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:42 p.m.