Triple
T1988267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mataf area |
E43189
|
entity |
| Predicate | hasCleaningRegime |
P32290
|
FINISHED |
| Object | continuous cleaning |
—
|
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: continuous cleaning | Statement: [Mataf area, hasCleaningRegime, continuous cleaning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCleaningRegime Context triple: [Mataf area, hasCleaningRegime, continuous cleaning]
-
A.
isRinseRequired
Indicates that an item or surface must be rinsed, typically with water, as a required step in a process or procedure.
-
B.
cleaningAction
chosen
Indicates an action in which an agent removes dirt, impurities, or unwanted substances from a target object, area, or entity.
-
C.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
D.
hasCheckAndBalanceWith
Indicates that two entities mutually monitor, limit, or counterbalance each other's powers or actions to prevent dominance or abuse.
-
E.
hasTypeOfManagement
Indicates that an entity is associated with or operates under a specified form or style of management.
- 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_69a88713ddc88190a969715658ebe7a8 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8ee02dc81908fec9fd8df7a4f40 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb79ad6888190be99943a9c73cf3e |
completed | March 7, 2026, 5:28 a.m. |
Created at: March 4, 2026, 7:37 p.m.