Triple
T3080893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Estates of the Holy Roman Empire |
E64252
|
entity |
| Predicate | hadNumberOfMembers |
P45752
|
FINISHED |
| Object | several hundred at peak |
—
|
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: several hundred at peak | Statement: [Imperial Estates of the Holy Roman Empire, hadNumberOfMembers, several hundred at peak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadNumberOfMembers Context triple: [Imperial Estates of the Holy Roman Empire, hadNumberOfMembers, several hundred at peak]
-
A.
hadMember
Indicates that an entity was formerly a member or part of another entity or group.
-
B.
hasMembers
Indicates that a group, organization, or collection includes certain entities as its members.
-
C.
previousNumberOfMembers
Indicates the number of members an entity had at an earlier or prior point in time.
-
D.
originalNumberOfMembers
Indicates the initial total count of members in a group or organization before any changes such as additions or removals.
-
E.
hasExtantMembers
Indicates that the referenced group, category, or lineage currently has living or existing members.
- 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_69ad857bb4c88190a4cf27893fcabed8 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1aaf6d48190af4f9106965589b0 |
completed | March 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69ad9debb6308190be28378ae1fc98af |
completed | March 8, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69ada0f6fef48190b13898be383a246b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:03 p.m.