Triple
T25979118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lennon Wall |
E646020
|
entity |
| Predicate | wasNotableDuring |
P8452
|
FINISHED |
| Object | Communist era in Czechoslovakia |
—
|
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: Communist era in Czechoslovakia | Statement: [Lennon Wall, wasNotableDuring, Communist era in Czechoslovakia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasNotableDuring Context triple: [Lennon Wall, wasNotableDuring, Communist era in Czechoslovakia]
-
A.
notableDuring
chosen
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
B.
wasProminent
Indicates that an entity held a position of significant importance, influence, or visibility within a particular context or period.
-
C.
wasProminentIn
Indicates that an entity was notably active, influential, or widely recognized within a particular field, context, or time period.
-
D.
hasNotablePeople
Indicates that certain people associated with an entity are distinguished or noteworthy in some recognized way.
-
E.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
- 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6050d0a808190837a1fd676f604f4 |
completed | May 2, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:53 a.m.