Triple
T9592003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-AGOR-28 |
E231442
|
entity |
| Predicate | prefixMeaning |
P27718
|
FINISHED |
| Object | T indicates operation by Military Sealift Command |
—
|
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: T indicates operation by Military Sealift Command | Statement: [T-AGOR-28, prefixMeaning, T indicates operation by Military Sealift Command]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prefixMeaning Context triple: [T-AGOR-28, prefixMeaning, T indicates operation by Military Sealift Command]
-
A.
hasPrefixMeaning
chosen
Indicates that one entity serves as a semantic prefix of another, contributing a specific meaning to the start of the second entity.
-
B.
birthNameMeaning
Indicates the semantic meaning or significance associated with a person's birth name.
-
C.
ordinalMeaningOfName
Indicates that a name refers to an entity’s position or rank in an ordered sequence (e.g., first, second, third).
-
D.
formerNameMeaning
Indicates that the meaning or interpretation of an entity’s previous name is being specified.
-
E.
letterMeaning
Indicates that a particular letter conveys a specific meaning, interpretation, or semantic content.
- 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_69ca8482884481908eccdfdf64d6fbf7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a10b85881908bfc783dcb7170aa |
completed | April 1, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a359788190b24f82399489f7fe |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:06 p.m.