Triple
T3654049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LMT |
E77487
|
entity |
| Predicate | hasSecurityIdentifierType |
P1285
|
FINISHED |
| Object | ticker symbol |
—
|
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: ticker symbol | Statement: [LMT, hasSecurityIdentifierType, ticker symbol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurityIdentifierType Context triple: [LMT, hasSecurityIdentifierType, ticker symbol]
-
A.
securityModelIdentifier
Indicates the specific security model or framework under which an entity, interaction, or policy is defined or governed.
-
B.
hasIdentifierSystem
chosen
Indicates that an entity is associated with a particular system or scheme used to assign and manage its identifiers.
-
C.
hasIdentity
Indicates that one entity is the same as, or is identified as, another specific entity or identifier.
-
D.
identifierTypeManaged
Indicates that one entity is responsible for administering or controlling the type or scheme of identifiers used for another entity.
-
E.
hasSecurityRelationship
Indicates a relationship in which one entity provides, manages, or is otherwise linked to the security or protection of another entity.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3b9164c81908938a4338430d193 |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb84650148190bf79231105e58d7f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.