Triple
T15675260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Paul Saints |
E377425
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | STP |
E377425
|
NE 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: STP | Statement: [St. Paul Saints, abbreviation, STP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: STP Context triple: [St. Paul Saints, abbreviation, STP]
-
A.
STP
STP is the three-letter ISO 3166-1 alpha-3 country code for São Tomé and Príncipe, an island nation in the Gulf of Guinea off Central Africa.
-
B.
STP
chosen
STP is the commonly used abbreviation for the St. Paul Saints, a professional baseball team based in Saint Paul, Minnesota.
-
C.
STP
STP is a U.S. Department of Defense program that manages and conducts spaceflight experiments and technology demonstrations.
-
D.
STP
STP is the three-letter station code used to identify St Paul’s Underground station on the London Underground network.
-
E.
STP-2
STP-2 was a U.S. Department of Defense Space Test Program mission that used a SpaceX Falcon Heavy rocket to deploy multiple experimental and technology demonstration payloads into orbit.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f2c996c8190a9ebe0e92608feaa |
completed | April 16, 2026, 2:53 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff6edd85148190b6d5c3981204dd77 |
completed | May 9, 2026, 5:29 p.m. |
Created at: April 10, 2026, 4:16 a.m.