Triple
T117121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Materials Division |
E2363
|
entity |
| Predicate | community |
P6194
|
FINISHED |
| Object | materials professionals in mechanical industries |
—
|
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: materials professionals in mechanical industries | Statement: [Materials Division, community, materials professionals in mechanical industries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: community Context triple: [Materials Division, community, materials professionals in mechanical industries]
-
A.
neighborhood
Indicates that one entity is located in close spatial proximity to another, typically within the same local area or district.
-
B.
notableCommunity
Indicates that an entity is a particularly prominent or significant member of a given community.
-
C.
town
Indicates that a location is classified or functions as a town within a given geographic or administrative context.
-
D.
hasNearbyCommunity
Indicates that one entity has another community located close to it in geographic or spatial terms.
-
E.
district
Indicates that one entity is an administrative or electoral district that geographically contains or governs another entity.
- 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_69a2506c5428819085c28a8884790e29 |
completed | Feb. 28, 2026, 2:18 a.m. |
| NER | Named-entity recognition | batch_69a257845c548190bfb49409988d1c57 |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a256456d908190b52c937fe6c4343f |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2578329d08190be82e004b8224d2b |
completed | Feb. 28, 2026, 2:48 a.m. |
Created at: Feb. 28, 2026, 2:24 a.m.