Triple
T802732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jud Fry |
E17162
|
entity |
| Predicate | notableProp |
P3488
|
FINISHED |
| Object | pornographic pictures |
—
|
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: pornographic pictures | Statement: [Jud Fry, notableProp, pornographic pictures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableProp Context triple: [Jud Fry, notableProp, pornographic pictures]
-
A.
notableProposition
Indicates that a subject is associated with a proposition, statement, or claim that is considered notable or significant in some context.
-
B.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
C.
notableAsset
chosen
Indicates that an entity possesses or is associated with an asset that is particularly significant, prominent, or noteworthy in relation to it.
-
D.
notablePrimary
Indicates that one entity is the main or most prominent example, instance, or representative of another entity.
-
E.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
- 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ace495348190aec66f35ea90bc89 |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa70973c8190adbf08302d1103a9 |
completed | March 1, 2026, 9:06 p.m. |
Created at: March 1, 2026, 7:38 p.m.