Triple
T23968578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Langwidere |
E604161
|
entity |
| Predicate | headStorage |
P154068
|
FINISHED |
| Object | cabinets in her palace |
—
|
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: cabinets in her palace | Statement: [Princess Langwidere, headStorage, cabinets in her palace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headStorage Context triple: [Princess Langwidere, headStorage, cabinets in her palace]
-
A.
headStatus
Indicates the current condition, role, or state of an entity in its capacity as a head or leader within a given context.
-
B.
headType
Indicates the specific kind or category of head associated with an entity (e.g., type of head part, head role, or head classification in a structure or system).
-
C.
headAttachment
Indicates that one entity is physically or structurally attached to the head or top part of another entity.
-
D.
headRetention
Indicates that an entity maintains or preserves its leadership, primary position, or top status over time or through a given event or process.
-
E.
heads
Indicates that one entity leads, directs, or is in charge of another entity, such as an organization, group, or initiative.
- 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d1da2ab08190bfe653fb5a9f2c96 |
completed | April 29, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 9:25 p.m.