Triple
T37310915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | kebaya |
E926201
|
entity |
| Predicate | continuedUseIn |
P176768
|
FINISHED |
| Object | 21st century fashion |
—
|
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: 21st century fashion | Statement: [kebaya, continuedUseIn, 21st century fashion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuedUseIn Context triple: [kebaya, continuedUseIn, 21st century fashion]
-
A.
continuedUseAfter
Indicates that an entity keeps using or applying another entity beyond an initial or expected point in time.
-
B.
eraOfContinuedUse
chosen
Indicates a time period during which something remains in ongoing, active use or operation.
-
C.
subsequentUse
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
-
D.
mainUseContinued
Indicates that the primary use or function of something persists or remains in effect over a subsequent period.
-
E.
continuedRelevanceIn
Indicates that something maintains its significance, applicability, or impact within a specified context, domain, or time period.
- 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_69f76eb1bc508190924e9fa5d8acdeb3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: May 3, 2026, 4:16 p.m.