Triple
T27756188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LoveLetter |
E701337
|
entity |
| Predicate | fileTypesTargeted |
P105373
|
FINISHED |
| Object | script files |
—
|
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: script files | Statement: [LoveLetter, fileTypesTargeted, script files]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fileTypesTargeted Context triple: [LoveLetter, fileTypesTargeted, script files]
-
A.
fileTypeCode
Indicates the specific classification or category code that identifies the type or format of a file.
-
B.
typicalFileType
Indicates that one entity is the usual or commonly associated file type for the other entity.
-
C.
fileTypeFamily
Indicates that one file type belongs to, or is categorized under, a broader family or group of related file types.
-
D.
filenameType
Indicates the type or category associated with a given filename (e.g., file format, role, or classification).
-
E.
typicalFileFormat
chosen
Indicates the usual or standard file format typically associated with or used for a given entity or context.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 4:23 p.m.