Triple
T5589944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Designer for Industry |
E146849
|
entity |
| Predicate | limitOnHolders |
P47665
|
FINISHED |
| Object | limited number of living holders |
—
|
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: limited number of living holders | Statement: [Royal Designer for Industry, limitOnHolders, limited number of living holders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitOnHolders Context triple: [Royal Designer for Industry, limitOnHolders, limited number of living holders]
-
A.
typicalNumberOfHolders
Indicates the usual or expected number of entities that hold or possess a given item, role, or resource.
-
B.
totalNumberOfHolders
Indicates the total count of distinct entities that hold or possess a given asset, item, or resource.
-
C.
eligibleHolders
Indicates which entities are permitted or qualified to hold or possess a given item, right, or role.
-
D.
numberOfHoldings
Indicates the quantity of distinct holdings or assets associated with an entity.
-
E.
officeHoldersNumberLimit
chosen
Indicates a constraint specifying the maximum number of individuals who may simultaneously hold a particular office or position.
- 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_69c009036c408190981a8d690b679b67 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0209ff5d88190843b6d134390ab71 |
completed | March 22, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69c01b16b9bc8190ab0b945507d90e05 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:38 p.m.