Triple
T9787151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Guard Party |
E237513
|
entity |
| Predicate | operatedInCommunity |
P88035
|
FINISHED |
| Object | Chinese American communities |
—
|
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: Chinese American communities | Statement: [Red Guard Party, operatedInCommunity, Chinese American communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedInCommunity Context triple: [Red Guard Party, operatedInCommunity, Chinese American communities]
-
A.
operationalCommunity
chosen
Indicates a relationship where entities are part of, or associated with, the same functioning or actively collaborating community in carrying out operations or activities.
-
B.
developedInCommunity
Indicates that something was created, built, or advanced through the participation, collaboration, or support of a particular community.
-
C.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
D.
hasNearbyCommunity
Indicates that one entity has another community located close to it in geographic or spatial terms.
-
E.
hasCommunityArea
Indicates that an entity is associated with, located in, or belongs to a particular community area.
- 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_69ca84da927881909bda80caecad6010 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda211b0608190bc8ceb905d02db83 |
completed | April 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69cd03d77c6c81909b675955bf113320 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:27 p.m.