Triple
T7376253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS North Carolina (BB-55) |
E170129
|
entity |
| Predicate | removedFromService |
P42074
|
FINISHED |
| Object | post-World War II drawdown |
—
|
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: post-World War II drawdown | Statement: [USS North Carolina (BB-55), removedFromService, post-World War II drawdown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removedFromService Context triple: [USS North Carolina (BB-55), removedFromService, post-World War II drawdown]
-
A.
removedFrom
Indicates that one entity has been taken away, extracted, or detached from another entity or context.
-
B.
serviceRetirement
chosen
Indicates that an entity ends or withdraws a service, marking it as no longer available or in active use.
-
C.
removedFromPublicDuties
Indicates that an entity has been taken out of roles or responsibilities that involve serving or representing the public.
-
D.
removedControlFrom
Indicates that one entity has taken away or revoked another entity’s authority, power, or control over something.
-
E.
removedBefore
Indicates that one entity was removed or taken away earlier in time than another specified entity or event.
- 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_69c68a5bfaac81909ce7f001dfb70c76 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1a8b18c8190ad1a19521eda2319 |
completed | March 27, 2026, 9:07 p.m. |
| PD | Predicate disambiguation | batch_69c6f02ee3e08190a7a00c981129b22c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:07 p.m.