Triple
T36480117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlie Andrews |
E898788
|
entity |
| Predicate | readsBook |
P63726
|
FINISHED |
| Object | Japanese phrasebook given by Hiro |
—
|
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: Japanese phrasebook given by Hiro | Statement: [Charlie Andrews, readsBook, Japanese phrasebook given by Hiro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readsBook Context triple: [Charlie Andrews, readsBook, Japanese phrasebook given by Hiro]
-
A.
readingOf
Indicates that one entity is an interpretation, measurement, or recorded value derived from another entity.
-
B.
readingOrganizer
Indicates that an entity is responsible for planning, managing, or coordinating reading-related activities or materials for others.
-
C.
readingAid
Indicates that one entity assists or facilitates another entity’s ability to read or engage in reading activities.
-
D.
reading
chosen
Indicates that an entity is engaged in the activity of interpreting and understanding written or printed material from another entity or source.
-
E.
readingSystem
Indicates a system or device that presents, interprets, or processes written or digital content for a user.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.