Triple
T35510668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rivet City |
E1026276
|
entity |
| Predicate | originalPurposeOfCarrier |
P75472
|
FINISHED |
| Object | pre-War military vessel |
—
|
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: pre-War military vessel | Statement: [Rivet City, originalPurposeOfCarrier, pre-War military vessel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalPurposeOfCarrier Context triple: [Rivet City, originalPurposeOfCarrier, pre-War military vessel]
-
A.
purposeOfOriginalDevelopment
Indicates the original intended purpose or goal for which something was first developed or created.
-
B.
cargoPurpose
Indicates the intended function or use for which a particular cargo is being transported.
-
C.
originalPrimaryUse
chosen
Indicates that something was first or chiefly intended to be used for a particular purpose or function.
-
D.
aircraftRoleDesignedFor
Indicates that an aircraft is specifically designed or intended to perform a particular role or function.
-
E.
usedAircraftOrigin
Indicates the place or source from which a used aircraft was originally obtained or came.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.