Triple
T30477557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vietnamese postage stamps |
E775482
|
entity |
| Predicate | sometimesUse |
P116266
|
FINISHED |
| Object | French language inscriptions |
—
|
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: French language inscriptions | Statement: [Vietnamese postage stamps, sometimesUse, French language inscriptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sometimesUse Context triple: [Vietnamese postage stamps, sometimesUse, French language inscriptions]
-
A.
oftenUse
Indicates that one entity frequently or regularly uses, employs, or utilizes another entity.
-
B.
isSometimesUsedFor
chosen
Indicates that something serves a particular purpose or function on some occasions, but not consistently or exclusively.
-
C.
likelyUse
Indicates that one entity is expected or probable to use, employ, or make use of another entity in a given context.
-
D.
sometimesEngageIn
Indicates that one entity engages in or performs an action or relationship with another entity on an occasional or intermittent basis, rather than consistently or always.
-
E.
endedUseWith
Indicates that an entity has stopped or terminated its use or association with another entity.
- 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_69f22497341481909c21ba329fadaa6b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68719f9c08190983e25b622e32c41 |
completed | May 2, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:12 p.m.