Triple
T7096666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GrandMosqueCourtyard |
E165345
|
entity |
| Predicate | cleaning |
P32290
|
FINISHED |
| Object | continuousCleaningOperations |
—
|
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: continuousCleaningOperations | Statement: [GrandMosqueCourtyard, cleaning, continuousCleaningOperations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cleaning Context triple: [GrandMosqueCourtyard, cleaning, continuousCleaningOperations]
-
A.
cleaningAction
chosen
Indicates an action in which an agent removes dirt, impurities, or unwanted substances from a target object, area, or entity.
-
B.
sweep
Indicates that an agent uses a tool or motion to clear or move unwanted material from a surface or area.
-
C.
clearingSystem
Indicates that one entity functions as the financial clearing mechanism or infrastructure used to settle transactions for another entity.
-
D.
notCleanedFor
Indicates that one entity has not been cleaned, maintained, or cleared in preparation for use by another entity.
-
E.
household
Indicates that two or more entities belong to or are part of the same household unit, typically sharing a residence and domestic life.
- 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_69c6887e8c10819091cee237560d32da |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e554d9f081909443be54eb501d25 |
completed | March 27, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:41 p.m.