Triple
T10504778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FT Weekend |
E247756
|
entity |
| Predicate | readingContext |
P94265
|
FINISHED |
| Object | leisurely weekend reading |
—
|
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: leisurely weekend reading | Statement: [FT Weekend, readingContext, leisurely weekend reading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readingContext Context triple: [FT Weekend, readingContext, leisurely weekend reading]
-
A.
readingFeature
Indicates that an entity possesses a characteristic, capability, or attribute specifically related to reading.
-
B.
reading
Indicates that an entity is engaged in the activity of interpreting and understanding written or printed material from another entity or source.
-
C.
readingApproach
Indicates the method, strategy, or manner in which an entity engages in reading a text.
-
D.
readingAid
Indicates that one entity assists or facilitates another entity’s ability to read or engage in reading activities.
-
E.
readingLocation
Indicates the place or position where a reading activity occurs or is associated with an 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5099f4dec8190a9851739c8bc9a69 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb919ea08190bcc1193e2014d437 |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:26 p.m.