Triple
T5004788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Drake |
E112462
|
entity |
| Predicate | laterService |
P13710
|
FINISHED |
| Object | United States Navy service as USS Ranger |
—
|
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: United States Navy service as USS Ranger | Statement: [HMS Drake, laterService, United States Navy service as USS Ranger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterService Context triple: [HMS Drake, laterService, United States Navy service as USS Ranger]
-
A.
laterFunction
Indicates that one function or event occurs after another in time.
-
B.
laterWork
Indicates that one work was created, published, or produced after another work in time.
-
C.
laterWithin
Indicates that one event or time point occurs later than another while still falling within a specified temporal interval or boundary.
-
D.
laterPolicy
Indicates that one policy occurs or becomes effective after another policy in time.
-
E.
laterStatus
chosen
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
- 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.