Triple
T14920656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County-class cruiser |
E371499
|
entity |
| Predicate | treatyLimited |
P55439
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [County-class cruiser, treatyLimited, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatyLimited Context triple: [County-class cruiser, treatyLimited, yes]
-
A.
treatyConcluded
Indicates that a formal agreement or treaty has been officially finalized and brought into force between the involved parties.
-
B.
treaty
Indicates a formal, negotiated agreement or pact established between entities, typically states or organizations, that defines mutual obligations, rights, or terms of cooperation.
-
C.
treatyConstraint
chosen
Indicates that an entity is subject to limitations, obligations, or conditions imposed by a treaty or formal international agreement.
-
D.
treatyType
Indicates the specific category or classification of a treaty that characterizes the nature of the agreement between parties.
-
E.
treatyScope
Indicates the range, subject matter, or extent of issues and obligations that a treaty covers or applies to.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded63121e48190b54eb2546acc3c93 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:33 a.m.