Triple
T2304859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian/Christmas |
E51814
|
entity |
| Predicate | IANAZoneDatabaseName |
P719
|
FINISHED |
| Object | Christmas |
—
|
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: Christmas | Statement: [Indian/Christmas, IANAZoneDatabaseName, Christmas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IANAZoneDatabaseName Context triple: [Indian/Christmas, IANAZoneDatabaseName, Christmas]
-
A.
timeZoneDatabase
Indicates that there is an association between something (such as a system, service, or region) and a specific time zone database it uses or is defined by.
-
B.
ianaZoneFile
Indicates that an entity is associated with, defined by, or described in a specific IANA DNS zone file.
-
C.
followsIANAZone
Indicates that one entity adopts or conforms to the time zone definition specified by the corresponding IANA time zone identifier of another entity.
-
D.
IANATimeZoneIdentifierExample
chosen
Indicates that the relationship provides an example of an IANA time zone identifier corresponding to a given time zone or context.
-
E.
timeZoneDatabaseFormat
Indicates that the relationship specifies the time zone using a standardized database format (such as the IANA/Olson time zone identifier).
- 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abce1f4f0c8190a714e4dcb8449f7e |
completed | March 7, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69abc58ce2a081908ce2f0cadd92e9f8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.