Triple
T18749908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/TC 176 |
E458499
|
entity |
| Predicate | standardsUserCommunity |
P7159
|
FINISHED |
| Object | manufacturing organizations |
—
|
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: manufacturing organizations | Statement: [ISO/TC 176, standardsUserCommunity, manufacturing organizations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardsUserCommunity Context triple: [ISO/TC 176, standardsUserCommunity, manufacturing organizations]
-
A.
notableUserCommunity
Indicates that a user has a significant or distinguished presence, role, or recognition within a particular community.
-
B.
communityAspect
Indicates that something pertains to, reflects, or influences the communal or social dimension of a group or community.
-
C.
usedByCommunity
chosen
Indicates that something is utilized or adopted collectively by a particular community.
-
D.
scriptUserCommunity
Indicates a relationship where a user participates in, belongs to, or is associated with a particular community within a script or scripted system.
-
E.
collaboratingCommunity
Indicates that two or more entities are actively working together toward shared goals or projects as part of a community relationship.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579ec71cc8190bb6d3fa6cca6dc8c |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.