Triple
T4656823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Honolulu (CL-48) |
E102428
|
entity |
| Predicate | outOfService |
P5870
|
FINISHED |
| Object | 1947 |
—
|
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: 1947 | Statement: [USS Honolulu (CL-48), outOfService, 1947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outOfService Context triple: [USS Honolulu (CL-48), outOfService, 1947]
-
A.
inService
Indicates that an entity is currently active, operational, or available for use in its intended role or function.
-
B.
doesNotOperate
Indicates that an entity is not functioning, active, or performing its intended operation in relation to another entity or context.
-
C.
operatingStatus
chosen
Indicates whether an entity is currently functioning, active, or in service versus inactive, closed, or out of service.
-
D.
inServiceFrom
Indicates the time or event from which an entity (such as a service, system, or asset) begins being operationally active or officially in use.
-
E.
openedForServiceOnLine
Indicates that an entity (such as a facility or station) began operating and providing service on a specified transit or service line.
- 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_69bd43d823288190952279faa0d1d066 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd63193a108190a7d9aec1d1d40cf8 |
completed | March 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69bd62126b0c81909ba3f21b21e30d54 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:14 p.m.