Triple
T36785864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSEA Protector |
E908908
|
entity |
| Predicate | hasNotableMarking |
P32310
|
FINISHED |
| Object | NTE hull prefix |
—
|
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: NTE hull prefix | Statement: [NSEA Protector, hasNotableMarking, NTE hull prefix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableMarking Context triple: [NSEA Protector, hasNotableMarking, NTE hull prefix]
-
A.
mayHaveMarkings
Indicates that an entity is permitted or able to possess certain markings or distinguishing signs.
-
B.
hasManMadeMarking
Indicates that an entity bears an artificial or human-created marking on its surface or structure.
-
C.
armorMarkings
Indicates that one entity bears specific markings, patterns, or insignia on its armor in relation to another entity or context.
-
D.
hasWingMarkings
Indicates that an entity possesses visible markings or patterns on its wings.
-
E.
distinctiveMarking
chosen
Indicates that one entity bears a unique or distinguishing visual feature or pattern that sets it apart from others.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.