Triple
T13122792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhutanese national flag |
E311765
|
entity |
| Predicate | earlierVersionIntroduced |
P11235
|
FINISHED |
| Object | 1947 |
—
|
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: 1947 | Statement: [Bhutanese national flag, earlierVersionIntroduced, 1947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierVersionIntroduced Context triple: [Bhutanese national flag, earlierVersionIntroduced, 1947]
-
A.
introducedFrom
Indicates that one entity was brought, originated, or caused to appear in a context, system, or environment by another entity.
-
B.
introducedBefore
Indicates that one entity was introduced or presented earlier in time than another entity.
-
C.
earlierVersionsCapability
Indicates that an entity has the ability to access, handle, or interact with earlier versions of another entity or resource.
-
D.
introducedWithVersion
chosen
Indicates that something first became available or was added starting from a specific version.
-
E.
messageIntroducedWith
Indicates that one message is presented or initiated by means of another message or introductory content.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9819840b881909b76022b4c4dcaed |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:07 p.m.