Triple
T30301802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DD |
E770669
|
entity |
| Predicate | hasNotationRole |
P52010
|
FINISHED |
| Object | indicates primary ship type |
—
|
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: indicates primary ship type | Statement: [DD, hasNotationRole, indicates primary ship type]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotationRole Context triple: [DD, hasNotationRole, indicates primary ship type]
-
A.
usesNotationFor
Indicates that one entity employs or adopts a particular notation system or symbolic representation for another entity.
-
B.
hasNameInNotation
Indicates that an entity is referred to by a specific name or label within a particular notation or symbolic system.
-
C.
notationRole
chosen
Indicates a role or function that an entity plays specifically within a system of notation or symbolic representation.
-
D.
hasNaturalRole
Indicates that an entity inherently fulfills or is assigned a particular function, purpose, or role within a natural or conceptual system.
-
E.
appearsInNotation
Indicates that one entity is represented, referenced, or depicted within the formal notation or symbolic system associated with 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a002dd4066c8190945a09ed82f44f3f |
completed | May 10, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_6a002b141f4081909999e14988105f3a |
completed | May 10, 2026, 6:52 a.m. |
Created at: April 29, 2026, 7:48 p.m.