Triple
T25713979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D-358 |
E644807
|
entity |
| Predicate | assignedAs |
P159001
|
FINISHED |
| Object | pennant number in Turkish naval service |
—
|
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: pennant number in Turkish naval service | Statement: [D-358, assignedAs, pennant number in Turkish naval service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assignedAs Context triple: [D-358, assignedAs, pennant number in Turkish naval service]
-
A.
assignedTo
Indicates that responsibility for a task, item, or role has been designated to a specific entity.
-
B.
assignedUnder
Indicates that one entity has been given responsibility, duty, or authority to act within the scope, supervision, or framework defined by another entity.
-
C.
assignedToWorkBy
Indicates that one entity is designated or directed by another entity to perform a specific job, task, or role.
-
D.
assignedToState
Indicates that something has been allocated or designated to a particular state or status.
-
E.
assignedByCustom
Indicates that something has been assigned or allocated to an entity through a user-defined or non-standard assignment process.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc6008a4819084116248372fdd78 |
completed | May 2, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69f480824a1c81908a8a492eedbc2596 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 9:22 p.m.