Triple
T2199440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ecuador Time |
E50453
|
entity |
| Predicate | usedInBusinessHours |
P36914
|
FINISHED |
| Object | Ecuadorian financial institutions |
—
|
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: Ecuadorian financial institutions | Statement: [Ecuador Time, usedInBusinessHours, Ecuadorian financial institutions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInBusinessHours Context triple: [Ecuador Time, usedInBusinessHours, Ecuadorian financial institutions]
-
A.
inOfficeDuring
Indicates that an entity holds or occupies an office or position throughout a specified time period.
-
B.
usedInWork
Indicates that something (such as a concept, method, material, or component) is employed or applied within a particular work, project, or creation.
-
C.
typicalBusinessHourStartLocalTime
Indicates the local time at which a business’s normal operating hours typically begin.
-
D.
isWorkHoliday
Indicates that a given day is designated as a non-working public or company holiday.
-
E.
usedBetween
Indicates that something serves as a means, medium, or shared resource connecting or operating jointly between two entities.
- F. None of above. chosen
Provenance (4 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda706f4819094de73e1d1d1f539 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf35c994819088a093c412931de4 |
completed | March 7, 2026, 6:01 a.m. |
Created at: March 4, 2026, 7:46 p.m.