Triple
T2184555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zulu time |
E49120
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Zulu hour |
E49120
|
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: Zulu hour | Statement: [Zulu time, alsoKnownAs, Zulu hour]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zulu hour Context triple: [Zulu time, alsoKnownAs, Zulu hour]
-
A.
Zulu time
chosen
Zulu time is a standardized time reference used worldwide—especially in aviation, military, and navigation—corresponding to Coordinated Universal Time (UTC) and denoted by the letter "Z."
-
B.
Nzaman
Nzaman is a dialect of the Fang language spoken by Fang communities in Central Africa.
-
C.
Madras Time
Madras Time was a former local time standard used in the Madras (now Chennai) region of India before the adoption of a unified national time zone.
-
D.
Bombay Time
Bombay Time was a former local time standard used in the city of Bombay (now Mumbai) before the adoption of a unified national time across India.
-
E.
Calcutta Time
Calcutta Time was a former local time standard used in Kolkata (then Calcutta) before the adoption of a unified national time zone in India.
- 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_69a88aa72d348190a9544bb5b8a4e71d |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf1009788190973cf94db68fbb6b |
completed | March 7, 2026, 6 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae5da963308190bcd0918b8317b3f6 |
completed | March 9, 2026, 5:42 a.m. |
Created at: March 4, 2026, 7:45 p.m.