Triple
T5467143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malkhut |
E122737
|
entity |
| Predicate | associatedVice |
P64246
|
FINISHED |
| Object | inertia (in some systems) |
—
|
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: inertia (in some systems) | Statement: [Malkhut, associatedVice, inertia (in some systems)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedVice Context triple: [Malkhut, associatedVice, inertia (in some systems)]
-
A.
associatedWithSee
Indicates a relationship where one entity is contextually or functionally linked to another through the act or concept of seeing or visual observation.
-
B.
associatedFort
Indicates that one entity is connected or linked to a particular fort, typically as its related or corresponding fortification.
-
C.
organizationAssociatedWith
Indicates that there is a formal or recognized connection or affiliation between an organization and another entity.
-
D.
associatedSingle
Indicates a one-to-one association where an entity is linked to exactly one corresponding related entity.
-
E.
associatedHeir
Indicates that one entity is designated or recognized as the heir connected to, or inheriting from, another entity.
- 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_69bd4643f16081908d7f29e08096115a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a370a88190b5d17b8a5387138d |
completed | March 20, 2026, 6:27 p.m. |
| PDg | Predicate description generation | batch_69bd927b0b4c81909d5e0f594822e3f9 |
completed | March 20, 2026, 6:31 p.m. |
Created at: March 20, 2026, 2:08 p.m.