Triple
T28281145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Prince |
E713148
|
entity |
| Predicate | mayBeRestrictedIn |
P90727
|
FINISHED |
| Object | political power |
—
|
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: political power | Statement: [Imperial Prince, mayBeRestrictedIn, political power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeRestrictedIn Context triple: [Imperial Prince, mayBeRestrictedIn, political power]
-
A.
mayHaveRestriction
chosen
Indicates that an entity can be subject to one or more limitations, conditions, or constraints, though such restrictions are not necessarily present.
-
B.
oftenRestrictedTo
Indicates that the use, occurrence, or applicability of something is frequently limited to a particular subset, context, or condition.
-
C.
eligibilityRestrictedBy
Indicates that an entity’s eligibility for something is limited, constrained, or conditioned by another specified factor or rule.
-
D.
hasHumanUseRestriction
Indicates that there is a limitation or condition on how something may be used by humans.
-
E.
mayRestrictActivity
Indicates that one entity has the authority or ability to limit, constrain, or prohibit certain actions or behaviors of another entity.
- 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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 11:23 p.m.