Triple
T8010419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Philadelphia |
E186473
|
entity |
| Predicate | statusAfterGrounding |
P127
|
FINISHED |
| Object | captured by Tripolitan forces |
—
|
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: captured by Tripolitan forces | Statement: [USS Philadelphia, statusAfterGrounding, captured by Tripolitan forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterGrounding Context triple: [USS Philadelphia, statusAfterGrounding, captured by Tripolitan forces]
-
A.
statusGrantedOn
Indicates the date or time at which a particular status was officially conferred or became effective for an entity.
-
B.
status
chosen
Indicates the current condition, state, or standing of an entity within a given context.
-
C.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
-
D.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
E.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
- 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_69ca82abaffc8190ab8af79cdbc31ab3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3d70caf8819090a9f98025470c0d |
completed | March 31, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:19 p.m.