Triple
T36312695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | /x/ |
E894103
|
entity |
| Predicate | moderationStyle |
P103777
|
FINISHED |
| Object | lightly moderated |
—
|
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: lightly moderated | Statement: [/x/, moderationStyle, lightly moderated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moderationStyle Context triple: [/x/, moderationStyle, lightly moderated]
-
A.
moderation
Indicates that an entity exercises restraint, balance, or avoidance of extremes in its actions, behavior, or use of resources.
-
B.
moderationMechanism
Indicates a process or system that regulates, controls, or adjusts the intensity, impact, or expression of something within a broader context.
-
C.
moderatorType
chosen
Indicates the role or category of moderation associated with an entity within a system or context.
-
D.
moderator
Indicates that one entity serves as a moderator for another entity, overseeing, managing, or facilitating its activities, interactions, or content.
-
E.
usesModerator
Indicates that an entity employs or relies on a moderator to oversee, regulate, or manage its interactions or processes.
- 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: May 3, 2026, 4:09 p.m.