Triple
T34324645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beijing commercial districts |
E880832
|
entity |
| Predicate | targetGroups |
P10541
|
FINISHED |
| Object | local residents |
—
|
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: local residents | Statement: [Beijing commercial districts, targetGroups, local residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetGroups Context triple: [Beijing commercial districts, targetGroups, local residents]
-
A.
targetsGroup
chosen
Indicates that an action, influence, or effect is directed toward a specific group as its intended recipient or focus.
-
B.
hostGroups
Indicates a grouping relationship where a host belongs to or is associated with one or more defined host groups.
-
C.
participantGroup
Indicates a relationship in which a set or group of entities jointly participate in a common event, activity, or interaction.
-
D.
allegedTargetGroup
Indicates that a group is claimed or suspected to be the intended target of an action, plan, or attack, without confirming that the claim is true.
-
E.
targetsProvision
Indicates that one entity is the intended recipient or beneficiary of a provision, service, or resource supplied by 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_69f349b9cd508190a996a616903b3e6d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
Created at: May 1, 2026, 1:58 a.m.