Triple
T2300629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Arkansas |
E51720
|
entity |
| Predicate | WWIServiceRole |
P12085
|
FINISHED |
| Object | convoy escort |
—
|
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: convoy escort | Statement: [USS Arkansas, WWIServiceRole, convoy escort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WWIServiceRole Context triple: [USS Arkansas, WWIServiceRole, convoy escort]
-
A.
cloudServiceName
Indicates the specific name assigned to a cloud-based service associated with an entity.
-
B.
serviceName
Indicates the specific name or identifier of a service associated with an entity or interaction.
-
C.
servicePrinciple
Indicates a relationship where one entity acts as a service principal, representing an application or service identity that can authenticate and be granted permissions to access resources on behalf of that service.
-
D.
systemRole
chosen
Indicates the functional position or responsibility that an entity holds within a larger system or structure.
-
E.
serviceClass
Indicates the classification or category of service associated with or provided by an entity in the relationship.
- 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_69a88b0a9f248190bcff941463d8f65a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcbabf01081908db3b42bc7c60444 |
completed | March 7, 2026, 6:54 a.m. |
| PD | Predicate disambiguation | batch_69abc58ad33c8190b8d68af41b6f5e07 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.