Triple
T38208607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altice N.V. |
E1009274
|
entity |
| Predicate | hasSecurityListing |
P202837
|
FINISHED |
| Object | ATC |
—
|
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: ATC | Statement: [Altice N.V., hasSecurityListing, ATC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurityListing Context triple: [Altice N.V., hasSecurityListing, ATC]
-
A.
isListedSecurity
Indicates that a security is officially admitted to trading on a recognized exchange or regulated market.
-
B.
listsSecurity
Indicates that an entity specifies or enumerates security-related items, settings, or attributes associated with another entity.
-
C.
hasSecurityPresence
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
-
D.
hasSecurityCategory
Indicates that an entity is associated with a particular security classification or category defining its protection or access level.
-
E.
hasSecurityDimension
Indicates that something possesses or is associated with a particular aspect or dimension of security.
- 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_69f76dc94fcc8190bd2f55e81f9d6527 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00c3362dcc819096e49b882709fddd |
completed | May 10, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_6a00c2e5cdd88190a5f2d0f6a843cd56 |
completed | May 10, 2026, 5:39 p.m. |
| PDg | Predicate description generation | batch_6a00c3355498819088253d5e5c17267f |
completed | May 10, 2026, 5:41 p.m. |
Created at: May 3, 2026, 4:30 p.m.