Triple
T38590998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hrothgar |
E932451
|
entity |
| Predicate | hasCustomizationLimitation |
P99
|
FINISHED |
| Object | restricted hairstyles |
—
|
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: restricted hairstyles | Statement: [Hrothgar, hasCustomizationLimitation, restricted hairstyles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomizationLimitation Context triple: [Hrothgar, hasCustomizationLimitation, restricted hairstyles]
-
A.
hasLimitation
chosen
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
B.
hasIntegrationLimitType
Indicates the type or nature of the integration limit applied in a given relationship or process.
-
C.
hasCustomizationPotential
Indicates that an entity can be adapted, modified, or personalized beyond its default configuration.
-
D.
hasCommunicationLimitation
Indicates that an entity is subject to some restriction, constraint, or reduced capacity in its ability to communicate.
-
E.
hasCustomizationArea
Indicates that an entity includes or is associated with a specific area or section dedicated to customization or configuration.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
Created at: May 3, 2026, 4:32 p.m.