Triple
T1492830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egyptian Navy |
E29618
|
entity |
| Predicate | serviceNumberLabel |
P28610
|
FINISHED |
| Object | personnel strength |
—
|
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: personnel strength | Statement: [Egyptian Navy, serviceNumberLabel, personnel strength]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceNumberLabel Context triple: [Egyptian Navy, serviceNumberLabel, personnel strength]
-
A.
serviceNumber
Indicates a unique identifying number assigned to a service, used to reference, track, or distinguish that service from others.
-
B.
serviceLabel
Indicates that a label or descriptive tag is assigned to a service to identify or categorize it.
-
C.
serviceBranch
Indicates the military or organizational branch in which an entity serves or is affiliated.
-
D.
serviceIn
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another entity.
-
E.
terminalNumber
Indicates the specific terminal identifier associated with an entity, such as a device, port, or connection point, within a larger system or network.
- 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_69a498dba1d8819093b46a3a8d2485f1 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6c4f0c88190a97ba4910c1a5d85 |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c48902808190a8028d359bcf123e |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c52c703c8190a56389b09d97659f |
completed | March 1, 2026, 11:01 p.m. |
Created at: March 1, 2026, 8:12 p.m.