Triple
T22143575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APT-P |
E547226
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | APT-E |
—
|
NE NERFINISHED |
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: APT-E | Statement: [APT-P, relatedTo, APT-E]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: APT-E Context triple: [APT-P, relatedTo, APT-E]
-
A.
APT-E
chosen
APT-E was an experimental British tilting high-speed train prototype developed in the 1970s to test advanced technologies for the Advanced Passenger Train program.
-
B.
APT-S
APT-S was a proposed production variant of British Rail’s experimental tilting Advanced Passenger Train, intended for regular high-speed passenger service.
-
C.
APT-P
APT-P was the experimental tilting prototype of British Rail’s Advanced Passenger Train, built to test high-speed rail technology in the 1970s–80s.
-
D.
APT
APT is a widely used command-line package management tool for installing, updating, and removing software on Debian-based Linux systems.
-
E.
APT
APT (Automatic Picture Transmission) is an analog satellite image broadcast format historically used by weather satellites to transmit low-resolution real-time imagery to ground receivers.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129c045448190b3d189cdb8c0d2fd |
completed | April 28, 2026, 9:42 p.m. |
Created at: April 16, 2026, 8:32 p.m.