Triple
T23995498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medawar |
E605176
|
entity |
| Predicate | partOfHistoricalCity |
P133942
|
FINISHED |
| Object | Beirut urban area |
—
|
NE NERFINISHED |
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: Beirut urban area | Statement: [Medawar, partOfHistoricalCity, Beirut urban area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfHistoricalCity Context triple: [Medawar, partOfHistoricalCity, Beirut urban area]
-
A.
partOfHistoricalArea
chosen
Indicates that one entity is located within or belongs to a designated historical area or heritage zone.
-
B.
passesHistoricCity
Indicates that a route, path, or entity travels through or goes by a city recognized for its historical significance.
-
C.
isHistoricalCity
Indicates that a city has historical significance, typically due to its age, past events, or preserved heritage.
-
D.
isInHistoricCenterOf
Indicates that one entity is located within the historic center area of another entity (typically a city or town).
-
E.
isHistoricCenterOf
Indicates that a place serves as the historically significant core or original central area of another location, typically a city or town.
- 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d38ec7cc8190b91cfa09f88dacc6 |
completed | April 29, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f1615994c48190a5de95d3f7e5cd0a |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:38 p.m.