Triple
T1248350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Museum of Beirut |
E26817
|
entity |
| Predicate | warDamagePeriod |
P25774
|
FINISHED |
| Object | 1975–1990 |
—
|
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: 1975–1990 | Statement: [National Museum of Beirut, warDamagePeriod, 1975–1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warDamagePeriod Context triple: [National Museum of Beirut, warDamagePeriod, 1975–1990]
-
A.
warPeriod
Indicates a time span during which a state of war or armed conflict is ongoing between parties.
-
B.
warDamage
Indicates damage that was caused as a direct consequence of war or armed conflict.
-
C.
worldWar
Indicates a large-scale armed conflict involving multiple nations across different regions of the world, typically encompassing numerous battles, alliances, and theaters of war.
-
D.
majorWar
Indicates a large-scale, intense armed conflict between major powers or involving substantial military forces and widespread impact.
-
E.
statusDuringWorldWarII
Indicates the role, condition, or classification an entity had specifically during the period of World War II.
- F. None of above. chosen
Provenance (4 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf827e088190a16d845cea14f2c9 |
completed | March 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6b075881908e867c25b5080e25 |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bc49693c8190978ec63a5171d342 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:47 p.m.