Triple
T24383523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACR-1 |
E614676
|
entity |
| Predicate | hullSeries |
P155996
|
FINISHED |
| Object | ACR |
—
|
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: ACR | Statement: [ACR-1, hullSeries, ACR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hullSeries Context triple: [ACR-1, hullSeries, ACR]
-
A.
hullFeature
Indicates a physical characteristic, structure, or component that is part of or present on the hull of an object (typically a vehicle or vessel).
-
B.
hullOrigin
Indicates the original source, location, or context from which a hull (such as a vessel’s or structure’s main body) is derived or constructed.
-
C.
hullConstruction
Indicates the process or activity of building, assembling, or forming the main body (hull) of a vessel or similar structure.
-
D.
hullNumber
Indicates the unique identifying number assigned to the hull of a ship or vessel.
-
E.
hullLayout
Indicates how the structural arrangement or configuration of a vessel’s hull is organized or laid out in relation to its components.
- F. None of above. chosen
Provenance (4 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294533b3881908c228a021c254006 |
completed | April 29, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:03 a.m.