Triple
T8611769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | scratch.mit.edu |
E203927
|
entity |
| Predicate | hasModeration |
P10370
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [scratch.mit.edu, hasModeration, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModeration Context triple: [scratch.mit.edu, hasModeration, yes]
-
A.
usesModerator
Indicates that an entity employs or relies on a moderator to oversee, regulate, or manage its interactions or processes.
-
B.
moderation
Indicates that an entity exercises restraint, balance, or avoidance of extremes in its actions, behavior, or use of resources.
-
C.
moderator
chosen
Indicates that one entity serves as a moderator for another entity, overseeing, managing, or facilitating its activities, interactions, or content.
-
D.
hasMAD
Indicates that an entity possesses or is associated with a specific MAD (e.g., a minimum acceptable distance, mean absolute deviation, or similarly defined MAD-related measure).
-
E.
hasHumanModification
Indicates that an entity has been altered, influenced, or modified as a result of human activity or intervention.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46fc31e08190aab5ab8f92f3315c |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.