Triple
T11728528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR |
E278838
|
entity |
| Predicate | exampleForm |
P12789
|
FINISHED |
| Object | SR 1 |
—
|
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: SR 1 | Statement: [SR, exampleForm, SR 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exampleForm Context triple: [SR, exampleForm, SR 1]
-
A.
usesForm
Indicates that one entity employs, applies, or operates through a particular form, format, or structured representation of something.
-
B.
exportForm
Indicates that one entity sends or transfers something (such as goods, data, or a document) out from its origin to another place, system, or jurisdiction in a specified format.
-
C.
formTreatment
Indicates that one entity creates, establishes, or defines a particular treatment or therapeutic regimen for another entity.
-
D.
typicalForm
chosen
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
-
E.
formsFrom
Indicates that one entity is created, derived, or takes shape as a result of another entity.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4d80ef881908cab956787ab07fd |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.