Triple
T35161573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pambansang Watawat |
E1015279
|
entity |
| Predicate | firstUnfurledOn |
P20170
|
FINISHED |
| Object | 1898-06-12 |
—
|
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: 1898-06-12 | Statement: [Pambansang Watawat, firstUnfurledOn, 1898-06-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUnfurledOn Context triple: [Pambansang Watawat, firstUnfurledOn, 1898-06-12]
-
A.
firstOpenedAt
Indicates the date and time at which something was initially opened for the first time.
-
B.
firstUsedOn
chosen
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or entity.
-
C.
firstReachedDate
Indicates the date on which a particular entity first achieved, accessed, or arrived at a specified state, location, or milestone.
-
D.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
-
E.
firstRelease
Indicates that one entity is the initial or earliest release (in time or sequence) of another entity, such as a product, work, or version.
- 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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.