Triple
T17568417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECS (Entity Component System) |
E427875
|
entity |
| Predicate | groupsAround |
P47305
|
FINISHED |
| Object | entities |
—
|
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: entities | Statement: [ECS (Entity Component System), groupsAround, entities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groupsAround Context triple: [ECS (Entity Component System), groupsAround, entities]
-
A.
socialGroupInvolved
Indicates that a particular social group participates in, is affected by, or is otherwise involved in the specified event or situation.
-
B.
groups
chosen
Indicates that one entity organizes, clusters, or associates multiple entities together as members of a collective set or category.
-
C.
groupTogether
Indicates that multiple entities are treated or arranged as a single collective unit or set.
-
D.
nearbyNativeGroups
Indicates that there are indigenous or native groups located in close geographic proximity to the referenced entity.
-
E.
communityType
Indicates the classification or category of community to which an entity belongs (e.g., urban, rural, online, professional).
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4592f29d08190bc3de905d35af849 |
completed | April 19, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fd7d048190b54ee4c6155612a5 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.