Triple
T13184079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US0846701086 |
E313801
|
entity |
| Predicate | hasSecurityIdentifier |
P6594
|
FINISHED |
| Object | 846701 |
—
|
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: 846701 | Statement: [US0846701086, hasSecurityIdentifier, 846701]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurityIdentifier Context triple: [US0846701086, hasSecurityIdentifier, 846701]
-
A.
hasSecurityClass
Indicates that an entity is assigned to or associated with a particular security classification level.
-
B.
hasSecurityRelationship
Indicates a relationship in which one entity provides, manages, or is otherwise linked to the security or protection of another entity.
-
C.
hasIdentity
chosen
Indicates that one entity is the same as, or is identified as, another specific entity or identifier.
-
D.
hasSecurityCategory
Indicates that an entity is associated with a particular security classification or category defining its protection or access level.
-
E.
hasSecurityPresence
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:15 p.m.