Triple
T250629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thai baht |
E5137
|
entity |
| Predicate | hasSecurityFeaturesOn |
P2368
|
FINISHED |
| Object | banknotes |
—
|
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: banknotes | Statement: [Thai baht, hasSecurityFeaturesOn, banknotes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurityFeaturesOn Context triple: [Thai baht, hasSecurityFeaturesOn, banknotes]
-
A.
securityFeature
chosen
Indicates that an entity provides, embodies, or is associated with a mechanism or property intended to enhance safety, protection, or defense against threats or vulnerabilities.
-
B.
hasCCTV
Indicates that one entity is equipped with or monitored by a CCTV (closed-circuit television) system installed or provided by another entity.
-
C.
securityMechanism
Indicates a relationship where one entity serves as a means or method to protect another entity from threats, vulnerabilities, or unauthorized actions.
-
D.
hasCheckAndBalanceWith
Indicates that two entities mutually monitor, limit, or counterbalance each other's powers or actions to prevent dominance or abuse.
-
E.
hasKeyInvention
Indicates that an entity possesses or is associated with a primary or crucial invention.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d38aba8819081d0958eb60ce27e |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b665f8c8190aac6fcbba2a0eebb |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.