Triple
T4081571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five-Power Treaty |
E87487
|
entity |
| Predicate | limitedTypeOfVessel |
P2429
|
FINISHED |
| Object | capital ships |
—
|
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: capital ships | Statement: [Five-Power Treaty, limitedTypeOfVessel, capital ships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitedTypeOfVessel Context triple: [Five-Power Treaty, limitedTypeOfVessel, capital ships]
-
A.
hasVesselType
Indicates that an entity is associated with or classified by a specific type of vessel (e.g., ship, boat, or container).
-
B.
usesVesselType
Indicates that an entity performs an activity or operation by employing a specific type or category of vessel.
-
C.
maximumVesselType
chosen
Indicates the highest or largest class, size, or category of vessel that is allowed, applicable, or associated in a given context.
-
D.
maxVesselTonnage
Indicates the maximum tonnage capacity that a vessel is allowed or designed to carry.
-
E.
hullType
Indicates the specific structural design or configuration of an object's hull, typically classifying how its outer body or shell is shaped or constructed.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc77dab481909bcf197daf2def59 |
completed | March 9, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.