Triple
T26108375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A51 |
E658601
|
entity |
| Predicate | notTypicallyShownTo |
P159958
|
FINISHED |
| Object | general public |
—
|
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: general public | Statement: [A51, notTypicallyShownTo, general public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notTypicallyShownTo Context triple: [A51, notTypicallyShownTo, general public]
-
A.
notTypically
Indicates that the referenced situation, behavior, or relationship does not usually or normally occur under standard or expected conditions.
-
B.
cannotShow
Indicates that one entity is unable or not permitted to display, reveal, or present another entity.
-
C.
notVisibleWhen
Indicates that one entity is not visible whenever a specified condition, state, or context involving another entity holds.
-
D.
notObservedIn
Indicates that a particular entity, event, or property has not been detected, recorded, or seen within a specified context, dataset, or environment.
-
E.
notTypicallyUsedFor
Indicates that something is generally not used for a particular purpose, function, or activity under normal circumstances.
- F. None of above. chosen
Provenance (4 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60779ae4c81909428c6d249cc0665 |
completed | May 2, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 8 p.m.