Triple
T16720562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auxiliary Division |
E406335
|
entity |
| Predicate | notoriousIn |
P110633
|
FINISHED |
| Object | Irish public opinion |
—
|
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: Irish public opinion | Statement: [Auxiliary Division, notoriousIn, Irish public opinion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notoriousIn Context triple: [Auxiliary Division, notoriousIn, Irish public opinion]
-
A.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
B.
hasMannerOfNotoriety
chosen
Indicates that an entity is known or recognized in a particular way, specifying the manner or type of its notoriety.
-
C.
notableSingle
Indicates that the subject is particularly recognized or distinguished for one specific, individual instance (such as a single work, event, or achievement).
-
D.
inceptionOfNotoriety
Indicates the point or event at which an entity first becomes widely known or gains significant public notoriety.
-
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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3874270748190ad7c3b3531293b60 |
completed | April 18, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.