Triple
T25908579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Curieux |
E652824
|
entity |
| Predicate | servedWithDistinction |
P178566
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [HMS Curieux, servedWithDistinction, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedWithDistinction Context triple: [HMS Curieux, servedWithDistinction, true]
-
A.
servedWithDistinctionIn
Indicates that an entity performed service in a particular role, organization, or context with notably high merit, honor, or excellence.
-
B.
servedWith
Indicates that one item is customarily presented, provided, or consumed together with another as an accompaniment or side.
-
C.
servedBefore
Indicates that one entity was served prior to another in time or sequence.
-
D.
served
Indicates that one entity provided a service, assistance, or role-based function to or for another entity.
-
E.
servedStrained
Indicates that something is provided or presented after having been filtered or strained to remove solids or impurities.
- 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f7117cf2188190b29e36fc1e342c60 |
completed | May 3, 2026, 9:12 a.m. |
Created at: April 22, 2026, 8:28 a.m.