Triple
T37615340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pearly King of Tower Hamlets |
E935903
|
entity |
| Predicate | nonHereditaryAspect |
P188757
|
FINISHED |
| Object | community-based selection |
—
|
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: community-based selection | Statement: [Pearly King of Tower Hamlets, nonHereditaryAspect, community-based selection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonHereditaryAspect Context triple: [Pearly King of Tower Hamlets, nonHereditaryAspect, community-based selection]
-
A.
nonHereditary
Indicates that a trait, condition, or status is not passed down genetically from parents to offspring.
-
B.
nonMaterialAspect
Indicates that one entity represents an immaterial, intangible, or conceptual aspect or property of another entity.
-
C.
nonAcnegenic
Indicates that a product or substance does not cause or promote acne formation on the skin.
-
D.
nonRole
Indicates that the specified entity does not hold, perform, or belong to the given role within the described context.
-
E.
nonTriggerFeature
Indicates that a feature or characteristic is present but does not initiate, cause, or trigger the associated event, process, or condition.
- F. None of above. chosen
Provenance (4 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_69f76ed16b748190ad6add183b1be688 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbacaea12c8190a4c99e64335f0e7e |
completed | May 6, 2026, 9:03 p.m. |
Created at: May 3, 2026, 4:18 p.m.