Triple
T21051325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Next of Kin |
E518588
|
entity |
| Predicate | hasReviewDescriptor |
P66549
|
FINISHED |
| Object | gripping |
—
|
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: gripping | Statement: [Next of Kin, hasReviewDescriptor, gripping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReviewDescriptor Context triple: [Next of Kin, hasReviewDescriptor, gripping]
-
A.
hasDescription
Indicates that an entity is associated with a textual description that explains or characterizes it.
-
B.
hasReviewReception
chosen
Indicates that an entity has received a critical or evaluative review describing how it was received or perceived.
-
C.
hasReviewPeriod
Indicates that an entity is associated with a specific time span during which it is subject to review or evaluation.
-
D.
hasCriticalDescriptor
Indicates that an entity is associated with a descriptor that marks it as critical, essential, or of high importance or severity.
-
E.
hasReviewBody
Indicates that an entity has an associated textual review content or body describing an evaluation or opinion about it.
- 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_69e0b5053ac48190921529544959e906 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fd7bd96c81909cb46419ad4e1222 |
completed | April 21, 2026, 4:30 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:35 p.m.