Triple
T1949242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Red Book |
E42122
|
entity |
| Predicate | binding |
P33754
|
FINISHED |
| Object | pocket-sized paperback |
—
|
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: pocket-sized paperback | Statement: [Little Red Book, binding, pocket-sized paperback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: binding Context triple: [Little Red Book, binding, pocket-sized paperback]
-
A.
bindingOn
Indicates that one party is legally or formally obligated to follow, accept, or be governed by a decision, rule, or agreement established by another.
-
B.
boundFor
Indicates that something is destined, directed, or scheduled to go toward a particular destination or target.
-
C.
holding
Indicates that one entity is physically grasping, carrying, or keeping another entity in its possession or control.
-
D.
traction
Indicates the degree to which one entity’s movement or influence effectively grips, pulls, or gains momentum relative to another entity or medium.
-
E.
held
Indicates that one entity physically grasped, carried, or kept another entity in its possession or control.
- 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_69a8870e08fc8190a319cbf2600db15f |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3315df481908f60cd87453fbc03 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff25a588190bb4cbc8df9fc6d64 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb32b748481909f1144cf0e4caefc |
completed | March 7, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:36 p.m.