Triple
T31716643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Naval Ship |
E809469
|
entity |
| Predicate | prefixPlacement |
P124850
|
FINISHED |
| Object | placed before the ship name |
—
|
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: placed before the ship name | Statement: [United States Naval Ship, prefixPlacement, placed before the ship name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prefixPlacement Context triple: [United States Naval Ship, prefixPlacement, placed before the ship name]
-
A.
canonicalPlacement
Indicates the standard or preferred position or arrangement of one entity relative to another within a defined structure or system.
-
B.
placementType
Indicates the specific manner or category in which something is positioned, arranged, or assigned within a given context.
-
C.
placementIn
Indicates that one entity is located or positioned within the spatial or structural bounds of another entity.
-
D.
prefixAssignedBy
Indicates that a specific prefix has been designated or allocated to an entity by a particular assigning authority or agent.
-
E.
positionBefore
chosen
Indicates that one entity occurs or is arranged earlier in order or sequence than another entity.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:17 p.m.