Triple
T27756201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LoveLetter |
E701337
|
entity |
| Predicate | modifiesRegistry |
P31226
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [LoveLetter, modifiesRegistry, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modifiesRegistry Context triple: [LoveLetter, modifiesRegistry, true]
-
A.
maintainsRegistryOf
Indicates that one entity is responsible for keeping and updating an official record or list of another set of entities or items.
-
B.
definesRegistry
Indicates that one entity establishes or specifies a registry in which another entity is recorded or managed.
-
C.
registryFunction
chosen
Indicates a function that is responsible for registering or recording entities, configurations, or events within a registry or central management system.
-
D.
relatedRegistry
Indicates that one registry has an association or linkage to another registry.
-
E.
registryFor
Indicates a relationship where one entity serves as an official registry or record-keeping authority for another entity or set of items.
- 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_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 4:23 p.m.