Triple
T7663832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navy Two |
E173576
|
entity |
| Predicate | callSignNumber |
P78631
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Navy Two, callSignNumber, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callSignNumber Context triple: [Navy Two, callSignNumber, 2]
-
A.
callSignForOffice
Indicates that a particular call sign is assigned to or used for a specific office or official position.
-
B.
callSignSpokenForm
Indicates the spoken or verbalized form used to refer to a particular call sign.
-
C.
callSignType
Indicates the classification or category of a call sign associated with an entity or communication.
-
D.
callSignForPerson
Indicates that a particular call sign is assigned to or used by a specific person.
-
E.
callSignStatus
Indicates the current operational or regulatory state associated with an entity’s call sign, such as whether it is active, reserved, expired, or otherwise designated.
- 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_69c699562484819086752091e3164a27 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7063dab1881909598b04999b8b690 |
completed | March 27, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69c7015f7430819099d3ea2781b7cee2 |
completed | March 27, 2026, 10:14 p.m. |
| PDg | Predicate description generation | batch_69c7063cfd78819095c6501fe8d57312 |
completed | March 27, 2026, 10:35 p.m. |
Created at: March 27, 2026, 4 p.m.