Triple
T8898087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quaker City |
E211854
|
entity |
| Predicate | publicity |
P9692
|
FINISHED |
| Object | widely publicized in American newspapers |
—
|
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: widely publicized in American newspapers | Statement: [Quaker City, publicity, widely publicized in American newspapers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicity Context triple: [Quaker City, publicity, widely publicized in American newspapers]
-
A.
sessionPublicity
Indicates that information about a session is made publicly accessible or promoted to a general audience.
-
B.
hasPublicPerception
Indicates that an entity is associated with a particular way it is viewed, judged, or regarded by the general public or society.
-
C.
publiclyDisplayed
Indicates that something is shown or made visible in a public context or setting, accessible to people at large.
-
D.
popularity
Indicates how widely liked, admired, or favored something or someone is by a group of people.
-
E.
notableExposure
chosen
Indicates that an entity has received significant public attention, visibility, or coverage, making it notably exposed or recognized.
- 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_69ca83918d3081909b326fa3750cb8c8 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc642618908190b3df50cbbabff93d |
completed | April 1, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2bfb38819083d5eb1af8ccf4d6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:54 p.m.