Triple
T34057574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hospital Rock |
E873403
|
entity |
| Predicate | hasFunctionDuringConflict |
P176299
|
FINISHED |
| Object | field hospital |
—
|
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: field hospital | Statement: [Hospital Rock, hasFunctionDuringConflict, field hospital]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFunctionDuringConflict Context triple: [Hospital Rock, hasFunctionDuringConflict, field hospital]
-
A.
hasFunctionDuring
Indicates that an entity performs or exhibits a specific function only within a specified time period or temporal context.
-
B.
implementedDuringConflict
Indicates that an action, policy, or measure was carried out while an active conflict or war was ongoing.
-
C.
hasOngoingConflict
Indicates that there is a current, unresolved state of opposition, dispute, or hostilities between the related entities.
-
D.
usedByDuringConflict
chosen
Indicates that one entity made practical use of another entity specifically in the context of a particular conflict or war.
-
E.
hasConflictCause
Indicates that one entity is the cause or source of a conflict involving another entity.
- 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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:52 a.m.