Triple
T78824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ich bin ein Berliner speech |
E1580
|
entity |
| Predicate | famousLine |
P492
|
FINISHED |
| Object | Ich bin ein Berliner |
—
|
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: Ich bin ein Berliner | Statement: [Ich bin ein Berliner speech, famousLine, Ich bin ein Berliner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousLine Context triple: [Ich bin ein Berliner speech, famousLine, Ich bin ein Berliner]
-
A.
notableQuote
chosen
Indicates that one entity is a significant or well-known quotation attributed to, recorded by, or strongly associated with another entity.
-
B.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
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.
servedByLine
Indicates that a transportation stop, station, or location is provided service by a specific transit line.
-
E.
hasPerson
Indicates that an entity is associated with or includes a specific person.
- 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_69a24c60d19c8190a1b6c105ca59ef5b |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24eb126b48190b410b859c1be99aa |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.