Triple
T26546725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Macedonian |
E671552
|
entity |
| Predicate | enteredUSServiceAs |
P161720
|
FINISHED |
| Object | USS Macedonian |
—
|
NE NERFINISHED |
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: USS Macedonian | Statement: [HMS Macedonian, enteredUSServiceAs, USS Macedonian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredUSServiceAs Context triple: [HMS Macedonian, enteredUSServiceAs, USS Macedonian]
-
A.
enteredUSAFServiceAs
Indicates that an individual began active service in the United States Air Force in a specified role, rank, or capacity.
-
B.
enteredService
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
C.
enteredServiceWithUnit
Indicates that an entity began its period of service or active duty while assigned to a specified unit.
-
D.
enteredServiceOn
Indicates the date or time when an entity first began active use, operation, or service.
-
E.
enteredServiceAsReplacementFor
Indicates that one entity began its period of service specifically to take over the role or function previously performed by another entity.
- 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6200ac60481909895c61d050b1338 |
completed | May 2, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 27, 2026, 1:44 a.m.