Triple
T6548868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pemuda Pancasila |
E151077
|
entity |
| Predicate | hasUniformElement |
P63681
|
FINISHED |
| Object | camouflage-pattern shirts |
—
|
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: camouflage-pattern shirts | Statement: [Pemuda Pancasila, hasUniformElement, camouflage-pattern shirts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUniformElement Context triple: [Pemuda Pancasila, hasUniformElement, camouflage-pattern shirts]
-
A.
isHomogeneous
Indicates that all elements or parts involved share the same type, nature, or characteristics, without significant variation among them.
-
B.
usesUniform
Indicates that one entity regularly wears or employs a standardized set of clothing or equipment designated as a uniform.
-
C.
hasElementType
chosen
Indicates that something is composed of or contains elements that are of a specified type.
-
D.
isNonUniform
Indicates that the property, distribution, or structure of something varies across its domain rather than remaining constant or uniform.
-
E.
usesElementsOf
Indicates that one entity incorporates, applies, or draws upon components, principles, or features derived from 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_69c687f3fd60819083bfa583e5bcfa71 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce07332481909a5a7964282eb776 |
completed | March 27, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69c6acf3e3708190b052ec774e607cb7 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:51 p.m.