Triple
T37283397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poltair School |
E925461
|
entity |
| Predicate | previousURN |
P201090
|
FINISHED |
| Object | 112037 |
—
|
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: 112037 | Statement: [Poltair School, previousURN, 112037]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousURN Context triple: [Poltair School, previousURN, 112037]
-
A.
previousRepository
Indicates that one repository directly precedes another in a version, history, or sequence of repositories.
-
B.
previousRecord
Indicates that one record directly precedes another in an ordered sequence of records.
-
C.
previousBranch
Indicates that one branch directly precedes another in an ordered sequence of branches.
-
D.
formerUrl
Indicates that one entity was previously identified or accessible via the URL represented by the other entity, but that URL is no longer current.
-
E.
previousVersionLocationOfAdoption
Indicates that one entity is the location where an earlier or prior version of another entity was adopted.
- F. None of above. chosen
Provenance (4 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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffc704e1e88190884928a6a5c55a87 |
completed | May 9, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69ffc6b483d881908ad872e25fa6abc5 |
completed | May 9, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69ffc70423f08190bd7c0625b21147a4 |
completed | May 9, 2026, 11:45 p.m. |
Created at: May 3, 2026, 4:16 p.m.