Triple
T7355229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ambon |
E169607
|
entity |
| Predicate | locatedInTimeZone |
P109
|
FINISHED |
| Object | WIT |
E633901
|
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: WIT | Statement: [Ambon, locatedInTimeZone, WIT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: WIT Context triple: [Ambon, locatedInTimeZone, WIT]
-
A.
WIT
chosen
WIT is the New York Stock Exchange ticker symbol for Wipro Limited, a major Indian multinational information technology services and consulting company.
-
B.
Witt
Witt is a surname most prominently associated with American television and film producer Paul Junger Witt, known for creating and producing numerous popular TV series.
-
C.
WIL
WIL is the standard abbreviation used for the Wilmington Blue Rocks minor league baseball team.
-
D.
WIL
WIL is the IATA airport code for Wilson Airport, a busy domestic and regional airport serving Nairobi, Kenya.
-
E.
WID
WID is the National Rail station code assigned to Widnes railway station in Cheshire, England.
- 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_69c68a59f2288190877ca15c19b1e822 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f10e71fc81909307ca39a61142d3 |
completed | March 27, 2026, 9:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7faa25960819084ecb6dbf9369ba5 |
completed | March 28, 2026, 3:58 p.m. |
Created at: March 27, 2026, 3:05 p.m.