Triple
T30342529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE Milestones program |
E771794
|
entity |
| Predicate | plaquesInstalledAt |
P134050
|
FINISHED |
| Object | sites of the achievements |
—
|
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: sites of the achievements | Statement: [IEEE Milestones program, plaquesInstalledAt, sites of the achievements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plaquesInstalledAt Context triple: [IEEE Milestones program, plaquesInstalledAt, sites of the achievements]
-
A.
hasPlaquePlacement
chosen
Indicates that a plaque has been positioned or installed at a specific location or on a particular object.
-
B.
hasNumberOfPlaques
Indicates the relationship that specifies how many plaques are associated with a given entity.
-
C.
hasPlaque
Indicates that an entity possesses or displays a plaque, such as a commemorative plate or a deposit on a surface.
-
D.
reErectedAt
Indicates that something was rebuilt or re-erected at a particular location or site.
-
E.
hasCommemorativePlaques
Indicates that one entity possesses or displays commemorative plaques associated with it.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f682046608819091b68c1f04f8f7fe |
completed | May 2, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:55 p.m.