Triple
T36084152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Textiles Monitoring Body |
E1043730
|
entity |
| Predicate | monitorsSector |
P752
|
FINISHED |
| Object | textiles |
—
|
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: textiles | Statement: [Textiles Monitoring Body, monitorsSector, textiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monitorsSector Context triple: [Textiles Monitoring Body, monitorsSector, textiles]
-
A.
monitors
chosen
Indicates that one entity observes, tracks, or checks the state, behavior, or performance of another entity over time.
-
B.
observedBySector
Indicates that something (such as an event, object, or phenomenon) is monitored, detected, or recorded by a specific sector or segment.
-
C.
sectorInspected
Indicates that a particular sector or area has been examined or checked, typically for compliance, safety, or condition.
-
D.
targetsSector
Indicates that an entity is directed toward, focused on, or intended to affect a particular economic or industry sector.
-
E.
tickerForSector
Indicates that a given stock ticker symbol belongs to or represents a company within a specified sector.
- 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.