Triple
T32290745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pohnpei Time |
E824958
|
entity |
| Predicate | isSimultaneousWith |
P4881
|
FINISHED |
| Object | Solomon Islands Time |
—
|
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: Solomon Islands Time | Statement: [Pohnpei Time, isSimultaneousWith, Solomon Islands Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSimultaneousWith Context triple: [Pohnpei Time, isSimultaneousWith, Solomon Islands Time]
-
A.
isMostlyConcurrentWith
Indicates that two events or intervals overlap in time for the majority of their durations, though not necessarily starting or ending together.
-
B.
overlapsWith
Indicates that two entities share a common part or region in space, time, or extent, but neither is completely contained within the other.
-
C.
coincidesWith
chosen
Indicates that two entities occupy the same position, time, or state such that they exactly overlap or occur together.
-
D.
meetsInTimePeriod
Indicates that two entities encounter or come together during a specified time period.
-
E.
meetsDuring
Indicates that one entity encounters or comes together with another while a specified event or time interval is in progress.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bd334be48190a0b648eb8b9f1899 |
completed | May 3, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:44 a.m.