Triple
T29265124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SI |
E741958
|
entity |
| Predicate | writingPosition |
P158941
|
FINISHED |
| Object | placed after the name of the awardee |
—
|
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: placed after the name of the awardee | Statement: [SI, writingPosition, placed after the name of the awardee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingPosition Context triple: [SI, writingPosition, placed after the name of the awardee]
-
A.
writingRegion
Indicates the region or area in which the writing or inscription is physically located or applied.
-
B.
writtenByPositionHolder
Indicates that something (such as a document, statement, or work) is authored or created by a person in their capacity as the holder of a specific position or office.
-
C.
writtenAtLocation
Indicates that an act of writing occurred at a specific physical or geographical location.
-
D.
writingOutput
Indicates that one entity produces or generates written content as an output, typically as the result of a writing or text-creation process.
-
E.
postPosition
chosen
Indicates that one entity is located behind or to the rear of another entity in space or sequence.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 12:44 p.m.