Triple
T6116792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sundanese people |
E136377
|
entity |
| Predicate | notableValue |
P22
|
FINISHED |
| Object | simplicity |
—
|
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: simplicity | Statement: [Sundanese people, notableValue, simplicity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableValue Context triple: [Sundanese people, notableValue, simplicity]
-
A.
notableFor
chosen
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
B.
notableField
Indicates the field, discipline, or area of activity for which an entity is especially known or distinguished.
-
C.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
D.
notableNumber
Indicates that a number associated with an entity is distinguished or significant in some notable way (e.g., record-setting, symbolic, or otherwise remarkable).
-
E.
notableKey
Indicates that the referenced key is of particular importance or prominence compared to other keys in the same context.
- 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05beb4cfc8190ab67a5338ec59cea |
completed | March 22, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:14 p.m.