Triple
T17628329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UP60 |
E429906
|
entity |
| Predicate | prefixLetters |
P46092
|
FINISHED |
| Object | UP |
—
|
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: UP | Statement: [UP60, prefixLetters, UP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prefixLetters Context triple: [UP60, prefixLetters, UP]
-
A.
precedesLetter
Indicates that one letter comes immediately before another letter in a specified ordering, such as the alphabet or a given sequence.
-
B.
namePrefix
chosen
Indicates that one entity is a prefix or leading part of another entity’s name.
-
C.
rootLetters
Indicates that one element specifies the fundamental root letters from which another linguistic form is derived.
-
D.
registrationPrefix
Indicates that an entity has a specific registration prefix code assigned to it as part of its official registration or identification.
-
E.
addressPrefix
Indicates that one address string serves as the starting portion or leading segment of another address.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46dbe3a308190a818d04f1a9b15f7 |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:52 a.m.