Triple
T28278526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuntunir Boi |
E713075
|
entity |
| Predicate | intendedReadingFormat |
P174204
|
FINISHED |
| Object | story collection |
—
|
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: story collection | Statement: [Tuntunir Boi, intendedReadingFormat, story collection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedReadingFormat Context triple: [Tuntunir Boi, intendedReadingFormat, story collection]
-
A.
readerFormat
chosen
Indicates the format or medium in which something is intended to be read or consumed.
-
B.
packageFormat
Indicates the format or type in which a package is structured, encoded, or delivered.
-
C.
intendedToBeReadAt
Indicates that something (such as a text, message, or content) is created or provided with the purpose of being read at a particular time, place, or context.
-
D.
presentedInFormat
Indicates that something is expressed, delivered, or made available using a particular format or representation.
-
E.
typicalRecognitionFormat
Indicates the usual or standard format in which something is recognized, identified, or acknowledged.
- 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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 27, 2026, 11:21 p.m.